Re: Skipping logical replication transactions on subscriber side

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(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>, Greg Nancarrow <gregn4422(at)gmail(dot)com>
Subject: Re: Skipping logical replication transactions on subscriber side
Date: 2021-09-30 20:05:35
Message-ID: 3163a085-66e6-426c-f97b-8df66980c7c4@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 30.09.21 07:45, Masahiko Sawada wrote:
> I've attached updated patches that incorporate all comments I got so
> far. Please review them.

I'm uneasy about the way the xids-to-be-skipped are presented as
subscriptions options, similar to settings such as "binary". I see how
that is convenient, but it's not really the same thing, in how you use
it, is it? Even if we share some details internally, I feel that there
should be a separate syntax somehow.

Also, what happens when you forget to reset the xid after it has passed?
Will it get skipped again after wraparound?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2021-09-30 20:09:56 Re: 002_types.pl fails on some timezones on windows
Previous Message Alvaro Herrera 2021-09-30 20:04:34 Re: prevent immature WAL streaming