From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Copy function for logical replication slots |
Date: | 2018-06-28 08:37:20 |
Message-ID: | 73bbc1ee-314f-85ab-2c25-f1670101d84d@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6/28/18 08:47, Michael Paquier wrote:
>>> There could be some cases where
>>> copying a physical slot also makes sense.
>> I've thought that but I didn't find concrete use case. That's why I
>> started with only logical slot.
> Let's imagine the case of a single base backup which is associated to a
> given replication slot, and that this backup is then used to spawn
> multiple standbys where each one of them needs a separate slot to
> consume changes at their pace. If you can copy the slot used in the
> first backup, then both nodes could consume it. That looks useful to
> me to make sure that both slots are based a consistent point.
I think this use case of cloning replicas would also be interesting in
the logical slot case.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2018-06-28 08:40:44 | Re: partition tree inspection functions |
Previous Message | Peter Eisentraut | 2018-06-28 08:14:57 | Re: ALTER TABLE on system catalogs |