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

From: Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com>
To: Luca Ferrari <fluca1978(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: max_connections different between primary and standby: is it possible?
Date: 2022-02-03 09:41:02
Message-ID: CAM+6J94m0_sXgBUC3K=cgoifhRyzoB7RY2B1pR5MV1x1dFE2=Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Feb 3, 2022, 3:07 PM Luca Ferrari <fluca1978(at)gmail(dot)com> 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 the primary
> server, where its value was 300.
>
> and the standby does not start until I raise also its max_connections.
> Why is PostgreSQL requiring the max_connections to be aligned between
> the primary and the standby?
>
> Thanks,
> Luca
>
>
>
> No. iirc, It has to be the same on all nodes in the physical replication
> setup.

But if vis pgbouncer, you can maintain the same max_connection but alter
> active front-end backend connections.
>

>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Abhishek Bhola 2022-02-03 09:43:47 Re: Subscription stuck at initialize state
Previous Message Luca Ferrari 2022-02-03 09:36:37 max_connections different between primary and standby: is it possible?