Re: Skipping logical replication transactions on subscriber side - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Skipping logical replication transactions on subscriber side
Date
Msg-id 6c5d98c6-879d-690c-b769-96aa162b93d9@enterprisedb.com
Whole thread Raw
In response to Re: Skipping logical replication transactions on subscriber side  (Greg Nancarrow <gregn4422@gmail.com>)
Responses Re: Skipping logical replication transactions on subscriber side  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On 13.12.21 04:12, Greg Nancarrow wrote:
> (ii) "Setting -1 means to reset the transaction ID"
> 
> Shouldn't it be explained what resetting actually does and when it can
> be, or is needed to be, done? Isn't it automatically reset?
> I notice that negative values (other than -1) seem to be regarded as
> valid - is that right?
> Also, what happens if this option is set multiple times? Does it just
> override and use the latest setting? (other option handling errors out
> with errorConflictingDefElem()).
> e.g. alter subscription sub skip (xid = 721, xid = 722);

Let's not use magic numbers and instead use a syntax that is more 
explicit, like SKIP (xid = NONE) or RESET SKIP or something like that.



pgsql-hackers by date:

Previous
From: "houzj.fnst@fujitsu.com"
Date:
Subject: RE: Column Filtering in Logical Replication
Next
From: Peter Eisentraut
Date:
Subject: Re: psql format output