BUG #17567: Unable to Set Max_Connection in Postgresql which has replicas - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #17567: Unable to Set Max_Connection in Postgresql which has replicas
Date
Msg-id 17567-2f6f580c03e97e0b@postgresql.org
Whole thread Raw
Responses Re: BUG #17567: Unable to Set Max_Connection in Postgresql which has replicas
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      17567
Logged by:          Poornima Venkatesan
Email address:      poornima3230@gmail.com
PostgreSQL version: 12.10
Operating system:   Windows/Linux
Description:

Hi Team,

PostgreSQL in 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, its 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


pgsql-bugs by date:

Previous
From: Richard Guo
Date:
Subject: Re: BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY
Next
From: Juan José Santamaría Flecha
Date:
Subject: Re: BUG #17567: Unable to Set Max_Connection in Postgresql which has replicas