From 4456e267ebecdbc27f7c7ddc174b1997355a496e Mon Sep 17 00:00:00 2001 From: Alexander Kukushkin Date: Mon, 22 Jul 2024 09:42:37 +0200 Subject: [PATCH] Patroni doesn't forece wal_log_hints anymore (#3109) We forgot to update it in https://github.com/patroni/patroni/pull/3063 --- docs/patroni_configuration.rst | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/patroni_configuration.rst b/docs/patroni_configuration.rst index 06d71426..7232ad46 100644 --- a/docs/patroni_configuration.rst +++ b/docs/patroni_configuration.rst @@ -62,7 +62,6 @@ There are some other Postgres parameters controlled by Patroni: - **port** - is set either from ``postgresql.listen`` or from ``PATRONI_POSTGRESQL_LISTEN`` environment variable - **cluster_name** - is set either from ``scope`` or from ``PATRONI_SCOPE`` environment variable - **hot_standby: on** -- **wal_log_hints: on** - for Postgres 9.4 and newer. To be on the safe side parameters from the above lists are not written into ``postgresql.conf``, but passed as a list of arguments to the ``pg_ctl start`` which gives them the highest precedence, even above `ALTER SYSTEM `__