Re: Connection slots reserved for replication - Mailing list pgsql-hackers

From Alexander Kukushkin
Subject Re: Connection slots reserved for replication
Date
Msg-id CAFh8B=km3F_a5Mf05WkNTSQ+EzGOk1WwPdzZVMsN4gAqEKVnkw@mail.gmail.com
Whole thread Raw
In response to Re: Connection slots reserved for replication  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
Responses Re: Connection slots reserved for replication  (Oleksii Kliukin <alexk@hintbits.com>)
List pgsql-hackers
Hi,

On Thu, 6 Dec 2018 at 00:55, Petr Jelinek <petr.jelinek@2ndquadrant.com> wrote:
> > Does excluding WAL senders from the max_connections limit and including max_wal_senders in MaxBackends also imply
thatwe need to add max_wal_senders to the list at xlog.c: CheckRequiredParameterValues, requiring its value on the
replicato be not lower than the one on the primary? 
> >
>
> I think it does, we need the proc slots for walsenders on the standby
> same way we do for normal backends.

You are absolutely right. Attaching the new version of the patch.

Regards,
--
Alexander Kukushkin

Attachment

pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: Problems with plan estimates in postgres_fdw
Next
From: Etsuro Fujita
Date:
Subject: Re: Problems with plan estimates in postgres_fdw