From b8d510a24a73c46fac02ccede8ff56c40be3dae8 Mon Sep 17 00:00:00 2001 From: ilja Date: Wed, 7 Dec 2022 11:36:01 +0100 Subject: [PATCH] typo in docs backup.md --- docs/docs/administration/backup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/administration/backup.md b/docs/docs/administration/backup.md index 63893c16a..cf2f7d1b0 100644 --- a/docs/docs/administration/backup.md +++ b/docs/docs/administration/backup.md @@ -29,7 +29,7 @@ [¹]: We assume the database name and user are both "akkoma". If not, you can find the correct name in your config files. [²]: You can recreate the `config/setup_db.psql` by running the `mix pleroma.instance gen` task again. You can ignore most of the questions, but make the database user, name, and password the same as found in your backed up config file. This will also create a new `config/generated_config.exs` file which you may delete as it is not needed. -[³]: `pg_restore` will add data before adding indexes. The indexes are added in alphabeticall order. There's one index, `activities_visibility_index` which may take a long time because it can't make use of an index that's only added later. You can significantly speed up restoration by skipping this index and add it afterwards. For that, you can do the following (we assume the akkoma.pgdump is in the directory you're running the commands): +[³]: `pg_restore` will add data before adding indexes. The indexes are added in alphabetical order. There's one index, `activities_visibility_index` which may take a long time because it can't make use of an index that's only added later. You can significantly speed up restoration by skipping this index and add it afterwards. For that, you can do the following (we assume the akkoma.pgdump is in the directory you're running the commands): ```sh pg_restore -l akkoma.pgdump > db.list