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(dot)albe(at)cybertec(dot)at>
To: Fabrice Chapuis <fabrice636861(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: problem during postgres restore: max_connections = 100 is a lower setting than on the primary server, where its value was 350
Date: 2026-03-02 14:36:30
Message-ID: 44166282b3516f33696f025ad9f5271244f78107.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Fabrice Chapuis 2026-03-02 16:13:22 Re: problem during postgres restore: max_connections = 100 is a lower setting than on the primary server, where its value was 350
Previous Message Laurenz Albe 2026-03-02 14:34:30 Re: upgrade from 13 to 16