diff options
| author | Igeljäger <igeljaeger@pm.me> | 2020-02-21 15:30:52 +0000 |
|---|---|---|
| committer | Igeljäger <igeljaeger@pm.me> | 2020-02-21 15:30:52 +0000 |
| commit | 1ed485ec1da435e32a8a867f1a0b5b9d3624095f (patch) | |
| tree | 4456a7492e36e25c10b6443f54a1cc18d7952d59 | |
| parent | 292031f6dd809accbcb3a5ba59d0100d807c5d72 (diff) | |
| download | pleroma-1ed485ec1da435e32a8a867f1a0b5b9d3624095f.tar.gz | |
added why doing a vacuum after restoring a backup is so important
| -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 |