public inbox for [email protected]
help / color / mirror / Atom feedFrom: Laurenz Albe <[email protected]>
To: Fabrice Chapuis <[email protected]>
To: Pgsql-admin <[email protected]>
Subject: Re: problem during postgres restore: max_connections = 100 is a lower setting than on the primary server, where its value was 350
Date: Mon, 02 Mar 2026 18:42:52 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAA5-nLBjwDeXTbsMxL-fwbfQ8asoCG0uG6hCMzPt2MLysdwFwQ@mail.gmail.com>
References: <CAA5-nLCdhiJW=zEBexw=NeDGirNGdKVWb-TEhRALM6+DCDRs6w@mail.gmail.com>
<[email protected]>
<CAA5-nLB9x9SW4KoPcukxAMj9N=wARJLHEBfkkGW+0Hh2FarnPA@mail.gmail.com>
<CAA5-nLBjwDeXTbsMxL-fwbfQ8asoCG0uG6hCMzPt2MLysdwFwQ@mail.gmail.com>
On Mon, 2026-03-02 at 17:13 +0100, Fabrice Chapuis wrote:
> I think the value of max_connections must be aligned with primary because
> the goal is to maintain this sizing in case of a failover and promotion of the standby.
Not every standby is for failover.
The technical reason is that the process array on the standby has to be at least
as big as on the primary (if you are setting "hot_standby = on").
> Why to be conservative with `max_connection` and not with shared buffer?
> If we're performing recovery on a machine with significantly fewer CPU and RAM
> resources than the original server, lowering these parameters could be an option
> because they reserve memory at starting.
Perhaps, but you cannot do it. If that is a requirement, use a connection pool.
Yours,
Laurenz Albe
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: problem during postgres restore: max_connections = 100 is a lower setting than on the primary server, where its value was 350
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox