Automatic translations update

i18n/translation-templates/docs/importing-postgres.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: matrix-docker-ansible-deploy \n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-02-13 10:32+0000\n"
+"POT-Creation-Date: 2026-07-15 04:33+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -25,7 +25,7 @@ msgid "You can manually import your database from a previous default installatio
 msgstr ""
 
 #: ../../../docs/importing-postgres.md:14
-#: ../../../docs/importing-postgres.md:38
+#: ../../../docs/importing-postgres.md:43
 msgid "**Notes**:"
 msgstr ""
 
@@ -57,98 +57,106 @@ msgstr ""
 msgid "Before doing the actual import, **you need to upload your Postgres dump file to the server** (any path is okay)."
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:28
+#: ../../../docs/importing-postgres.md:29
+msgid "Do not import into a database that already contains tables (e.g. one that a service has already initialized and used). As the [official Synapse backup guide](https://element-hq.github.io/synapse/latest/usage/administration/backups.html) puts it: at best this will error, at worst it will lead to subtle database inconsistencies. Import into an empty (freshly created) database instead."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:31
+msgid "**Note for Synapse users restoring an older backup**: if the server kept running (and users kept chatting) after the backup you are restoring was made, truncate the `e2e_one_time_keys_json` table after importing and before starting Synapse. Restoring an older backup can otherwise cause already-used one-time keys to be re-issued, leading to message decryption errors for your users. You can do this by [getting a database terminal](maintenance-postgres.md#getting-a-database-terminal), connecting to the Synapse database (`\\c synapse`) and running `TRUNCATE e2e_one_time_keys_json;`. Clients will generate and upload fresh one-time keys automatically."
+msgstr ""
+
+#: ../../../docs/importing-postgres.md:33
 msgid "Importing"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:30
+#: ../../../docs/importing-postgres.md:35
 msgid "To import, run this command (make sure to replace `SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:40
+#: ../../../docs/importing-postgres.md:45
 msgid "`SERVER_PATH_TO_POSTGRES_DUMP_FILE` must be a file path to a Postgres dump file on the server (not on your local machine!)"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:41
+#: ../../../docs/importing-postgres.md:46
 msgid "`postgres_default_import_database` defaults to `matrix`, which is useful for importing multiple databases (for dumps made with `pg_dumpall`). If you're importing a single database (e.g. `synapse`), consider changing `postgres_default_import_database` accordingly"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:42
+#: ../../../docs/importing-postgres.md:47
 msgid "after importing a large database, it's a good idea to run [an `ANALYZE` operation](https://www.postgresql.org/docs/current/sql-analyze.html) to make Postgres rebuild its database statistics and optimize its query planner. You can easily do this via the playbook by running `just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze` (see [Vacuuming PostgreSQL](maintenance-postgres.md#vacuuming-postgresql) for more details)."
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:44
+#: ../../../docs/importing-postgres.md:49
 msgid "Troubleshooting"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:46
+#: ../../../docs/importing-postgres.md:51
 msgid "Table Ownership"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:48
+#: ../../../docs/importing-postgres.md:53
 msgid "A table ownership issue can occur if you are importing from a Synapse installation which was both:"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:50
+#: ../../../docs/importing-postgres.md:55
 msgid "migrated from SQLite to Postgres, and"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:51
+#: ../../../docs/importing-postgres.md:56
 msgid "used a username other than 'synapse'"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:53
+#: ../../../docs/importing-postgres.md:58
 msgid "In this case you may run into the following error during the import task:"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:59
+#: ../../../docs/importing-postgres.md:64
 msgid "where `synapse_user` is the database username from the previous Synapse installation."
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:61
+#: ../../../docs/importing-postgres.md:66
 msgid "This can be verified by examining the dump for ALTER TABLE statements which set OWNER TO that username:"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:73
+#: ../../../docs/importing-postgres.md:78
 msgid "It can be worked around by changing the username to `synapse`, for example by using `sed`:"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:79
+#: ../../../docs/importing-postgres.md:84
 msgid "This uses sed to perform an 'in-place' (`-i`) replacement globally (`/g`), searching for `synapse_user` and replacing with `synapse` (`s/synapse_user/synapse`). If your database username was different, change `synapse_user` to that username instead. Expand search/replace statement as shown in example above, in case of old user name like `matrix` — replacing `matrix` only would… well — you can imagine."
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:81
+#: ../../../docs/importing-postgres.md:86
 msgid "Note that if the previous import failed with an error it may have made changes which are incompatible with re-running the import task right away; if you do so it may fail with an error such as:"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:87
+#: ../../../docs/importing-postgres.md:92
 msgid "Repeat import"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:89
+#: ../../../docs/importing-postgres.md:94
 msgid "In this case you can use the command suggested in the import task to clear the database before retrying the import:"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:97
+#: ../../../docs/importing-postgres.md:102
 msgid "Now on your local machine run `just run-tags setup-postgres` to prepare the database roles etc."
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:99
+#: ../../../docs/importing-postgres.md:104
 msgid "If not, you probably get this error. `synapse` is the correct table owner, but the role is missing in database."
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:105
+#: ../../../docs/importing-postgres.md:110
 msgid "Once the database is clear and the ownership of the tables has been fixed in the SQL file, the import task should succeed."
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:107
+#: ../../../docs/importing-postgres.md:112
 msgid "Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths (or even better, copy this line from your terminal)"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:113
+#: ../../../docs/importing-postgres.md:118
 msgid "Hints"
 msgstr ""
 
-#: ../../../docs/importing-postgres.md:115
+#: ../../../docs/importing-postgres.md:120
 msgid "To open psql terminal run `/matrix/postgres/bin/cli`"
 msgstr ""