Message-ID: <44166282b3516f33696f025ad9f5271244f78107.camel@cybertec.at>
Subject: Re: problem during postgres restore: max_connections = 100 is a
 lower setting than on the primary server, where its value was 350
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Fabrice Chapuis <fabrice636861@gmail.com>, Pgsql-admin
	 <pgsql-admin@lists.postgresql.org>
Date: Mon, 02 Mar 2026 15:36:30 +0100
In-Reply-To: 
 <CAA5-nLCdhiJW=zEBexw=NeDGirNGdKVWb-TEhRALM6+DCDRs6w@mail.gmail.com>
References: 
	<CAA5-nLCdhiJW=zEBexw=NeDGirNGdKVWb-TEhRALM6+DCDRs6w@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/44166282b3516f33696f025ad9f5271244f78107.camel%40cybertec.at>
Precedence: bulk

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_con=
n
> max_connections setting: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
350
> That is the value registered from the primary. But the primary is not int=
ended to be connected during this restore.
> primary_conninfo is desactivated.
>=20
> Is there a trick to change decrease this value and start the instance.

Why bother?

Leave max_connections at 350.

Yours,
Laurenz Albe