On Thu, Jun 28, 2018 at 03:34:00PM +0900, Masahiko Sawada wrote:
> On Thu, Jun 28, 2018 at 12:29 PM, Michael Paquier <michael@paquier.xyz> wrote:
>> Hm. Shouldn't the original slot copied be owned by the process doing
>> the copy with ReplicationSlotAcquire?
>
> Right, it should do and release it before creating new one.
Yes, or MyReplicationSlot would not like that.
>> 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.
--
Michael