Re: Skipping logical replication transactions on subscriber side

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Greg Nancarrow <gregn4422(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com>, "osumi(dot)takamichi(at)fujitsu(dot)com" <osumi(dot)takamichi(at)fujitsu(dot)com>, Alexey Lesovsky <lesovsky(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Skipping logical replication transactions on subscriber side
Date: 2021-12-17 09:53:48
Message-ID: 6c5d98c6-879d-690c-b769-96aa162b93d9@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2021-12-17 10:08:37 Re: psql format output
Previous Message houzj.fnst@fujitsu.com 2021-12-17 09:46:14 RE: Column Filtering in Logical Replication