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

From Alexander Kukushkin
Subject Re: Connection slots reserved for replication
Date
Msg-id CAFh8B=nbh4gbFCiT-jpjth60QJC1pKoWkvgke+7di-FgAduGLQ@mail.gmail.com
Whole thread Raw
In response to Re: Connection slots reserved for replication  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Connection slots reserved for replication  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List pgsql-hackers
Hi,

2018-09-14 12:23 GMT+02:00 Masahiko Sawada <sawada.mshk@gmail.com>:

>> 2. If we know that this is neither superuser nor replication connection, we
>> should check that there are at least (superuser_reserved_connections +
>> NumWalSenders() - max_wal_senders) connection slots are available.
>
> You wanted to mean (superuser_reserved_connections + max_wal_senders -
> NumWalSenders()) in the second point?

Sure, my bad. Did a mistake when writing an email, but in the attached
file it looks good.

>
> One argrable point of the second option could be that it breaks
> backward compatibility of the parameter configurations. That is, the
> existing systems need to re-configure the max_connections. So it might
> be better to take the first option with
> replication_reservd_connections = 0 by default.

Please find attached the new version of the patch, which introduces
replication_reservd_connections GUC

Regards,
--
Alexander Kukushkin

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pgsql: Improve autovacuum logging for aggressive andanti-wraparound ru
Next
From: Andrew Dunstan
Date:
Subject: Re: XMLNAMESPACES (was Re: Clarification of nodeToString() use cases)