mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2026-07-16 02:42:16 +10:00
Automatic translations update
This commit is contained in:
github-actions[bot]
committed by
GitHub
GitHub
parent
5a9e34c563
commit
38de158bad
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: matrix-docker-ansible-deploy \n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2026-05-19 07:40+0000\n"
|
||||
"POT-Creation-Date: 2026-07-14 11:57+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"
|
||||
@@ -149,69 +149,73 @@ msgid "Restoring a backup made this way can be done by [importing it](importing-
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:79
|
||||
msgid "Upgrading PostgreSQL"
|
||||
msgid "**Note for Synapse users**: the [official Synapse backup guide](https://element-hq.github.io/synapse/latest/usage/administration/backups.html) recommends that the `e2e_one_time_keys_json` table either not be backed up, or be truncated after restoring (before Synapse is started). The full-server dump command above does include it, so if you ever restore a backup that is older than the server's current state, remember to truncate that table as described in [the importing guide](importing-postgres.md)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:81
|
||||
msgid "Unless you are using an [external Postgres server](configuring-playbook-external-postgres.md), this playbook initially installs Postgres for you."
|
||||
msgid "Upgrading PostgreSQL"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:83
|
||||
msgid "Once installed, the playbook attempts to preserve the Postgres version it starts with. This is because newer Postgres versions cannot start with data generated by older Postgres versions."
|
||||
msgid "Unless you are using an [external Postgres server](configuring-playbook-external-postgres.md), this playbook initially installs Postgres for you."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:85
|
||||
msgid "Upgrades must be performed manually."
|
||||
msgid "Once installed, the playbook attempts to preserve the Postgres version it starts with. This is because newer Postgres versions cannot start with data generated by older Postgres versions."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:87
|
||||
msgid "Upgrades must be performed manually."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:89
|
||||
msgid "The playbook can upgrade your existing Postgres setup with the following command:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:93
|
||||
#: ../../../docs/maintenance-postgres.md:95
|
||||
msgid "**The old Postgres data directory is backed up** automatically, by renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to a different path, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_auto_upgrade_backup_data_path=/another/disk/matrix-postgres-before-upgrade\"`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:95
|
||||
#: ../../../docs/maintenance-postgres.md:97
|
||||
msgid "The auto-upgrade-backup directory stays around forever, until you **manually decide to delete it**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:97
|
||||
#: ../../../docs/maintenance-postgres.md:99
|
||||
msgid "As part of the upgrade, the database is dumped to `/tmp`, an upgraded and empty Postgres server is started, and then the dump is restored into the new server. To use a different directory for the dump, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_dump_dir=/directory/to/dump/here\"`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:99
|
||||
#: ../../../docs/maintenance-postgres.md:101
|
||||
msgid "To save disk space in `/tmp`, the dump file is gzipped on the fly at the expense of CPU usage. If you have plenty of space in `/tmp` and would rather avoid gzipping, you can explicitly pass a dump filename which doesn't end in `.gz`. Example: `--extra-vars=\"postgres_dump_name=matrix-postgres-dump.sql\"`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:101
|
||||
#: ../../../docs/maintenance-postgres.md:103
|
||||
msgid "**All databases, roles, etc. on the Postgres server are migrated**. However, other components that depend on specific Postgres versions (like the [Postgres Backup](configuring-playbook-postgres-backup.md) service) may need to be updated after the upgrade by using `just install-all`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:103
|
||||
#: ../../../docs/maintenance-postgres.md:105
|
||||
msgid "Tuning PostgreSQL"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:105
|
||||
#: ../../../docs/maintenance-postgres.md:107
|
||||
msgid "PostgreSQL can be [tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) to make it run faster. This is done by passing extra arguments to the Postgres process."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:107
|
||||
#: ../../../docs/maintenance-postgres.md:109
|
||||
msgid "The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) **already does some tuning by default**, which matches the [tuning logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) done by websites like https://pgtune.leopard.in.ua/. You can manually influence some of the tuning variables. These parameters (variables) are injected via the `postgres_postgres_process_extra_arguments_default` variable."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:109
|
||||
#: ../../../docs/maintenance-postgres.md:111
|
||||
msgid "Most users should be fine with the automatically-done tuning. However, you may wish to:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:111
|
||||
#: ../../../docs/maintenance-postgres.md:113
|
||||
msgid "**adjust the automatically-determined tuning parameters manually**: change the values for the tuning variables defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see `postgres_max_connections`, `postgres_data_storage` etc). These variables are ultimately passed to Postgres via a `postgres_postgres_process_extra_arguments_default` variable"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:113
|
||||
#: ../../../docs/maintenance-postgres.md:115
|
||||
msgid "**turn automatically-performed tuning off**: override it like this: `postgres_postgres_process_extra_arguments_default: []`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:115
|
||||
#: ../../../docs/maintenance-postgres.md:117
|
||||
msgid "**add additional tuning parameters**: define your additional Postgres configuration parameters in `postgres_postgres_process_extra_arguments_custom`. See `postgres_postgres_process_extra_arguments_default` defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) for inspiration"
|
||||
msgstr ""
|
||||
|
||||
Reference in New Issue
Block a user