Re: problem during postgres restore: max_connections = 100 is a lower setting than on the primary server, where its value was 350

public inbox for [email protected]  
help / color / mirror / Atom feed

From: Fabrice Chapuis <[email protected]>
To: Pgsql-admin <[email protected]>
To: Laurenz Albe <[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, 2 Mar 2026 17:13:22 +0100
Message-ID: <CAA5-nLBjwDeXTbsMxL-fwbfQ8asoCG0uG6hCMzPt2MLysdwFwQ@mail.gmail.com> (raw)
In-Reply-To: <CAA5-nLB9x9SW4KoPcukxAMj9N=wARJLHEBfkkGW+0Hh2FarnPA@mail.gmail.com>
References: <CAA5-nLCdhiJW=zEBexw=NeDGirNGdKVWb-TEhRALM6+DCDRs6w@mail.gmail.com>
	<[email protected]>
	<CAA5-nLB9x9SW4KoPcukxAMj9N=wARJLHEBfkkGW+0Hh2FarnPA@mail.gmail.com>

Thanks for answering Laurenz,

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.
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.

These are the questions I've been asking to myself.

On Mon, Mar 2, 2026 at 4:20 PM Fabrice Chapuis <[email protected]>
wrote:

> Thanks for answering Laurenz,
>
> 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.
> 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.
>
> These are the questions I've been asking to myself.
>
> On Mon, Mar 2, 2026 at 3:36 PM Laurenz Albe <[email protected]>
> wrote:
>
>> On Mon, 2026-03-02 at 11:27 +0100, Fabrice Chapuis wrote:
>> > I got this error from restoring a backup on a recovery machine.
>> > I got error about the max_connections that I changed from 350 to 100.
>> > in the control file the value is 350
>> > /usr/pgsql-17/bin/pg_controldata -D /pgdata/pgsql/17/main/ | grep
>> max_conn
>> > max_connections setting:              350
>> > That is the value registered from the primary. But the primary is not
>> intended to be connected during this restore.
>> > primary_conninfo is desactivated.
>> >
>> > Is there a trick to change decrease this value and start the instance.
>>
>> Why bother?
>>
>> Leave max_connections at 350.
>>
>> 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: <CAA5-nLBjwDeXTbsMxL-fwbfQ8asoCG0uG6hCMzPt2MLysdwFwQ@mail.gmail.com>

* 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