From: | Alexander Kukushkin <cyberdemn(at)gmail(dot)com> |
---|---|
To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Connection slots reserved for replication |
Date: | 2018-09-21 11:43:28 |
Message-ID: | CAFh8B=nDLOTypkGkc7SGbCryZ1zxe3gOU3ALf2jp4GOd2vTpGg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 20 September 2018 at 08:18, Kyotaro HORIGUCHI
<horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>
> Instaed, we can iterally "reserve" connection slots for the
> specific use by providing ProcGlobal->walsenderFreeProcs. The
> slots are never stolen for other usage. Allowing additional
> walsenders comes after all the slots are filled to grab an
> available "normal" slot, it works as the same as the current
> behavior when walsender_reserved_connectsions = 0.
>
> What do you think about this?
Sounds reasonable, please see the updated patch.
Regards,
--
Alexander Kukushkin
Attachment | Content-Type | Size |
---|---|---|
replication_reserved_connections-v3.patch | text/x-patch | 7.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | David Steele | 2018-09-21 11:44:06 | Re: pgsql: Make WAL segment size configurable at initdb time. |
Previous Message | Hubert Zhang | 2018-09-21 11:32:16 | Re: Proposal for disk quota feature |