From: Igeljäger <igeljaeger@pm.me>
Date: Fri, 21 Feb 2020 15:30:52 +0000 (+0000)
Subject: added why doing a vacuum after restoring a backup is so important
X-Git-Url: https://git.squeep.com/?a=commitdiff_plain;h=1ed485ec1da435e32a8a867f1a0b5b9d3624095f;p=akkoma

added why doing a vacuum after restoring a backup is so important
---

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