Re: max_connections different between primary and standby: is it possible?

Julien Rouhaud writes: > On Thu, Feb 03, 2022 at 05:39:57PM +0530, Bharath Rupireddy wrote: >> ... Instead, it would be better >> if the server emits a single log with all the insufficient >> parameters(max_connections, max_worker_processes, max_wal_senders, >> max_prepared_transactions and max_lo

Re: max_connections different between primary and standby: is it possible?

On Thu, Feb 03, 2022 at 05:39:57PM +0530, Bharath Rupireddy wrote: > > Agree that the standby should atleast have the capacity that the > primary has in terms of resources. But what I don't like about that > code is calling RecoveryRequiresIntParameter for each parameter > separately and crashing

Re: max_connections different between primary and standby: is it possible?

On Thu, Feb 3, 2022 at 3:17 PM Julien Rouhaud wrote: > > Hi, > > On Thu, Feb 03, 2022 at 10:36:37AM +0100, Luca Ferrari wrote: > > Hi all, > > running PostgreSQL 14, physical replication with slot, after changing > > (increasing) the max_connections on the primary, I had this message at > > a rest

Re: max_connections different between primary and standby: is it possible?

Hi, On Thu, Feb 03, 2022 at 10:36:37AM +0100, Luca Ferrari wrote: > Hi all, > running PostgreSQL 14, physical replication with slot, after changing > (increasing) the max_connections on the primary, I had this message at > a restart from the standby: > > DETAIL: max_connections = 100 is a lower

Re: max_connections different between primary and standby: is it possible?

On Thu, Feb 3, 2022, 3:07 PM Luca Ferrari wrote: > Hi all, > running PostgreSQL 14, physical replication with slot, after changing > (increasing) the max_connections on the primary, I had this message at > a restart from the standby: > > DETAIL: max_connections = 100 is a lower setting than on t

Re: max_connections

and this one as well. just to keep it in the thread. Improving Postgres Connection Scalability: Snapshots - Microsoft Tech Community On Fri, 4 Jun 2021 at 00:14

Re: max_connections

ok, running too many connections without recycling has an overhead. no wonder pgbouncer is all over as a sidecar :) In case anyone is interested, this blog is a great read. Analyzing the Limits of Connection Scalability in Postgres - Microsoft Tech Community

Re: max_connections parameter: too_many_connections error

> On Sep 17, 2019, at 8:43 AM, Shital A wrote: > > Hello, > > We are working on a payments systems which uses postgreSql 9.6 as backend DB > and blockchain technology. The database is setup in HA in master-standby mode > using pacemaker on Linux 7.6. > > We are new to postgres and need help

RE: max_connections parameter: too_many_connections error

1. How can we decide on optimal value for max_connections for a given setup/server? I checked many posts saying that even 1000 is considered as a very high value but we are hitting the error too_many_connections due to Max_connections value limit. I have one set at 1000 but I usually top out

RE: Max_connections limit

Hi, If you reckon the application initiates such a large number of concurrent connections, I'd suggest you configure a connection pooler to avoid the connection overhead by PostgreSQL. max_connections will be the parameter you are looking at to configure but ensure it is configured in conjuncti