diff options
| author | Ivan Tashkinov <ivantashkinov@gmail.com> | 2020-03-11 09:15:55 +0300 |
|---|---|---|
| committer | Ivan Tashkinov <ivantashkinov@gmail.com> | 2020-03-11 09:15:55 +0300 |
| commit | 972889550da0f623693eeb3b2d1ca3025501e5eb (patch) | |
| tree | 175d795fcd44230b20913d162d96516bbab81989 /docs/administration/backup.md | |
| parent | 5fc92deef37dcc4db476520d89dd79e616356e63 (diff) | |
| parent | 953aece84866a89bd3de8f6d3f5d30e2f9cfb4f3 (diff) | |
| download | pleroma-972889550da0f623693eeb3b2d1ca3025501e5eb.tar.gz | |
Merge remote-tracking branch 'remotes/origin/develop' into 1560-non-federating-instances-routes-restrictions
Diffstat (limited to 'docs/administration/backup.md')
| -rw-r--r-- | docs/administration/backup.md | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/docs/administration/backup.md b/docs/administration/backup.md index 692aa7368..be57bf74a 100644 --- a/docs/administration/backup.md +++ b/docs/administration/backup.md @@ -18,9 +18,8 @@ 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; +9. Run `sudo -Hu postgres vacuumdb --all --analyze-in-stages`. This will quickly generate the statistics so that postgres can properly plan queries. + [^1]: Prefix with `MIX_ENV=prod` to run it using the production config file. ## Remove |