mirror of https://github.com/zulip/zulip.git
cb2d0ff32b
PostgreSQL 11 and below used a configuration file names `recovery.conf` to manage replicas and standbys; support for this was removed in PostgreSQL 12[1], and the configuration parameters were moved into the main `postgresql.conf`. Add `zulip.conf` settings for the primary server hostname and replication username, so that the complete `postgresql.conf` configuration on PostgreSQL 14 can continue to be managed, even when replication is enabled. For consistency, also begin writing out the `recovery.conf` for PostgreSQL 11 and below. In PostgreSQL 12 configuration and later, the `wal_level = hot_standby` setting is removed, as `hot_standby` is equivalent to `replica`, which is the default value[2]. Similarly, the `hot_standby = on` setting is also the default[3]. Documentation is added for these features, and the commentary on the "Export and Import" page referencing files under `puppet/zulip_ops/` is removed, as those files no longer have any replication-specific configuration. [1]: https://www.postgresql.org/docs/current/recovery-config.html [2]: https://www.postgresql.org/docs/12/runtime-config-wal.html#GUC-WAL-LEVEL [3]: https://www.postgresql.org/docs/12/runtime-config-replication.html#GUC-HOT-STANDBY |
||
|---|---|---|
| .. | ||
| authentication-methods.md | ||
| deployment.md | ||
| email-gateway.md | ||
| email.md | ||
| expensive-migrations.md | ||
| export-and-import.md | ||
| giphy-gif-integration.md | ||
| index.md | ||
| install-existing-server.md | ||
| install.md | ||
| maintain-secure-upgrade.md | ||
| management-commands.md | ||
| mobile-push-notifications.md | ||
| multiple-organizations.md | ||
| password-strength.md | ||
| postgresql.md | ||
| requirements.md | ||
| security-model.md | ||
| settings.md | ||
| ssl-certificates.md | ||
| troubleshooting.md | ||
| upgrade-or-modify.md | ||
| upload-backends.md | ||
| video-calls.md | ||