diff options
| author | Alexander Strizhakov <alex.strizhakov@gmail.com> | 2020-02-29 11:34:50 +0300 |
|---|---|---|
| committer | Alexander Strizhakov <alex.strizhakov@gmail.com> | 2020-02-29 11:34:50 +0300 |
| commit | 814b275af7748df6bd11dfc6be1b4efce8d5ae70 (patch) | |
| tree | e18b30dfa6eb020e593dbe1cc0e649da3e6ed394 /docs/administration | |
| parent | 6b012ddd69aec0f85c22ad91dbb76e05f2edaf58 (diff) | |
| parent | aad057a2d6baaa342f47f55d330f0731277dac06 (diff) | |
| download | pleroma-814b275af7748df6bd11dfc6be1b4efce8d5ae70.tar.gz | |
Merge branch 'develop' into gun
Diffstat (limited to 'docs/administration')
| -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 |