Re: Connection slots reserved for replication
Alexander Kukushkin <cyberdemn@gmail.com>
From: Alexander Kukushkin <cyberdemn@gmail.com>
To: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2018-09-21T11:43:28Z
Lists: pgsql-hackers
Attachments
- replication_reserved_connections-v3.patch (text/x-patch) patch v3
Hi, On 20 September 2018 at 08:18, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.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
Commits
-
Fix description of WAL record XLOG_PARAMETER_CHANGE
- b7ec820559b6 12.0 landed
-
Move max_wal_senders out of max_connections for connection slot handling
- ea92368cd1da 12.0 landed