On Thu, Jun 28, 2018 at 11:51:20AM +0900, Masahiko Sawada wrote: > A use case I imagined is for investigations for example. I mean that > when replication collision occurs on subscriber there is no way to see > what replicated data is conflicting (perhaps error log helps it but is > not detailed) and there is no way to advance a replication origin in > order to exactly skip to apply conflicting data. By creating a new > logical slot with a different output plugin at the same LSN, we can > see what data a replication slot will decode (and send) and those LSNs > as well. This function will help for that purpose.
Hm. Shouldn't the original slot copied be owned by the process doing the copy with ReplicationSlotAcquire? There could be some cases where copying a physical slot also makes sense. -- Michael
signature.asc
Description: PGP signature
