diff options
| author | Ivan Tashkinov <ivantashkinov@gmail.com> | 2020-02-22 09:31:43 +0300 |
|---|---|---|
| committer | Ivan Tashkinov <ivantashkinov@gmail.com> | 2020-02-22 09:31:43 +0300 |
| commit | 8f0ca19b9cafeedc70df2d60bd7bd7c6bf7aa160 (patch) | |
| tree | f14a1ef01c90124b33b2866117ed2995e32ab369 /docs/administration/backup.md | |
| parent | 0d14c3f41053f97d23fa9295745a817c08010969 (diff) | |
| parent | 114e7b764ed5ae03211cca40e7b19f33292b3d1c (diff) | |
| download | pleroma-8f0ca19b9cafeedc70df2d60bd7bd7c6bf7aa160.tar.gz pleroma-8f0ca19b9cafeedc70df2d60bd7bd7c6bf7aa160.zip | |
Merge remote-tracking branch 'remotes/origin/develop' into 1505-threads-federation
# Conflicts:
# CHANGELOG.md
# config/config.exs
Diffstat (limited to 'docs/administration/backup.md')
| -rw-r--r-- | docs/administration/backup.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/administration/backup.md b/docs/administration/backup.md index 685c45128..692aa7368 100644 --- a/docs/administration/backup.md +++ b/docs/administration/backup.md @@ -18,7 +18,9 @@ 6. Run `sudo -Hu postgres pg_restore -d <pleroma_db> -v -1 </path/to/backup_location/pleroma.pgdump>` 7. If you installed a newer Pleroma version, you should run `mix ecto.migrate`[^1]. This task performs database migrations, if there were any. 8. Restart the Pleroma service. - +9. After you've restarted Pleroma, you will notice that postgres will take up more cpu resources than usual. A lot in fact. To fix this you must do a VACUUM ANLAYZE. This can also be done while the instance is still running like so: + $ sudo -u postgres psql pleroma_database_name + pleroma=# VACUUM ANALYZE; [^1]: Prefix with `MIX_ENV=prod` to run it using the production config file. ## Remove |