BUG #17567: Unable to Set Max_Connection in Postgresql which has replicas

On Wed, Aug 3, 2022 at 12:48 PM PG Bug reporting form <
noreply@postgresql.org> wrote:

Please advise us on the steps on how to configure and set Max_Connections
in
Replica DB servers.

This list is meant for reporting bugs only, please send questions like so
to pgsql-general@lists.postgresql.org.

Regards,

Juan José Santamaría Flecha

Hi Team,

PostgreSQL in our Production environment is configured using primary and
secondary DB servers via Patroni. We have requirement to explicitly to set
Max_Connection as 300 overriding default value. If we set Max_Connections in
postgresql.config, it is getting reset post restart of Patroni.

Please advise us on the steps on how to configure and set Max_Connections in
Replica DB servers.

Thanks & Regards,
Poornima V

On Wed, Aug 3, 2022 at 4:43 PM Juan José Santamaría Flecha <
juanjo.santamaria@gmail.com> wrote:

Hey,
It is not a bug.
If you are using patroni, you should change your parameters in patroni
configuration yaml file, so the changes are reflected in your Distributed
Configuration Store. If you would look at the Patroni documentation (
https://patroni.readthedocs.io/en/latest/SETTINGS.html) you can find a
note, that parameters like max_connections are stored in DCS and applied on
all Patroni nodes overwriting settings from postgresql.conf. Also if
Postgres was bootstrapped by Patroni, postgresql.conf itself should have a
note:

# Do not edit this file manually!
# It will be overwritten by Patroni!

Hope it helps.

Cheers,
Mateusz

czw., 4 sie 2022 o 10:21 Poornima Venkatesan <poornima3230@gmail.com>
napisał(a):