pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: tanghy.fnst@fujitsu.com <tanghy.fnst@fujitsu.com>
Cc: vignesh C <vignesh21@gmail.com>
Cc: Greg Nancarrow <gregn4422@gmail.com>
Cc: houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
Cc: osumi.takamichi@fujitsu.com <osumi.takamichi@fujitsu.com>
Cc: Alexey Lesovsky <lesovsky@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Skipping logical replication transactions on subscriber side
Date: Thu, 27 Jan 2022 14:42:19 +0100
Message-ID: <cfcc839b-0851-4112-a7c5-1543d129e811@enterprisedb.com> (raw)
In-Reply-To: <CAD21AoDL5Vbi438UOJs=Z4O_5HevVa7aeJzCM2jHcXDb48PZhw@mail.gmail.com>
References: <CAA4eK1LoUULzh-WreQe3TcL5s5oUG3c1bibC8rSThqknvvKvPQ@mail.gmail.com>
	<CAA4eK1+qwob8N2Ks4i=8=cBJ5trqr3cNuB99-9dRKkMLLZ_tvA@mail.gmail.com>
	<9c28c90c-f5b5-d8b9-e9b3-6af21b976725@enterprisedb.com>
	<CAA4eK1+9yXkWkJSNtWYV2rG7QNAnoAt+eNH0PexoSP9ZQmXKPg@mail.gmail.com>
	<78a7ef21-bb27-f78a-521e-94ddb4d5c669@enterprisedb.com>
	<CAKFQuwY=7v9xyb4A4m6dBnTJyRXvOFnpqnTgauL1US=WO_Ukdg@mail.gmail.com>
	<CAD21AoBf5ZY9Gv07GR10c-f8NmdeX+zvYEbp7JL3kMh9OB6Rig@mail.gmail.com>
	<CAKFQuwa4GUDTqkjdmhrt=4XREX=GTjFhfoRdG6X0uocwtpGvxA@mail.gmail.com>
	<CAD21AoBoMaCMTga7LYN7JEvhBs_gBqa8RLgxM3GBMxRn6f+8qA@mail.gmail.com>
	<CAA4eK1LANoQHgP4Rfe04nf1RWNhwckJ-+Osp+hmm7JuYZ+Wufw@mail.gmail.com>
	<CAD21AoCU2PLm+SxdOdUMpjgHioMB6baOoxqNi_XHD6QQJF+RKg@mail.gmail.com>
	<CAD21AoDHCAD9anS6ZzNyG1-B7F_BvzyiNfZ=O-tMEdwmKhfW8A@mail.gmail.com>
	<CAA4eK1J6VNwofqvs+kLCdf_wWztFLzet0d0N64xOoyx9DgivAw@mail.gmail.com>
	<CAD21AoDL5Vbi438UOJs=Z4O_5HevVa7aeJzCM2jHcXDb48PZhw@mail.gmail.com>

On 26.01.22 05:05, Masahiko Sawada wrote:
>> I think it is okay to clear after the first successful application of
>> any transaction. What I was not sure was about the idea of giving
>> WARNING/ERROR if the first xact to be applied is not the same as
>> skip_xid.
> Do you prefer not to do anything in this case?

I think a warning would be sensible.  If the user specifies to skip a 
certain transaction and then that doesn't happen, we should at least say 
something.





view thread (590+ messages)  latest in thread

Message-ID: <cfcc839b-0851-4112-a7c5-1543d129e811@enterprisedb.com>
Permalink:  ../cfcc839b-0851-4112-a7c5-1543d129e811@enterprisedb.com/
Also on:    postgresql.org/message-id/cfcc839b-0851-4112-a7c5-1543d129e811@enterprisedb.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: peter.eisentraut@enterprisedb.com, sawada.mshk@gmail.com, amit.kapila16@gmail.com, david.g.johnston@gmail.com, tanghy.fnst@fujitsu.com, vignesh21@gmail.com, gregn4422@gmail.com, houzj.fnst@fujitsu.com, osumi.takamichi@fujitsu.com, lesovsky@gmail.com
  Subject: Re: Skipping logical replication transactions on subscriber side
  In-Reply-To: <cfcc839b-0851-4112-a7c5-1543d129e811@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox