Re: [HACKERS] Function to move the position of a replication slot - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Function to move the position of a replication slot
Date
Msg-id 11042.1504323427@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Function to move the position of a replication slot  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] Function to move the position of a replication slot  (Michael Paquier <michael.paquier@gmail.com>)
Re: [HACKERS] Function to move the position of a replication slot  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 8/31/17 08:19, Magnus Hagander wrote:
>> I think that, in the end, covered all the comments?

> I didn't see any explanation of what this would actually be useful for.
> I suppose you could skip over some changes you don't want replicated,
> but how do you find to what position to skip?

Um ... I can see how you might expect to skip some events in a logical
replication stream and have a chance of things not being utterly broken.
But how can that work for physical replication?  Missed updates are
normally spelled "unrecoverable data corruption" at that level.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Function to move the position of a replication slot
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] Secondary index access optimizations