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: houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
Cc: tanghy.fnst@fujitsu.com <tanghy.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>
Cc: Greg Nancarrow <gregn4422@gmail.com>
Subject: Re: Skipping logical replication transactions on subscriber side
Date: Sun, 10 Oct 2021 16:04:31 +0200
Message-ID: <2a9287f4-a870-ee93-d032-b93d7e908ba7@enterprisedb.com> (raw)
In-Reply-To: <CAD21AoC_AdB5i4OVHu-RWxSFr4nYgcEp2XhVv7i-hpYsX=ANHw@mail.gmail.com>
References: <CAD21AoCgfka7rDREXRNQZJ4_GnHTTwqP6JMpaD5aBPhbtoeS8A@mail.gmail.com>
	<CAA4eK1JKf2Jejg1abuuU-Gx8Dkw0tey4Jiz5ACyQJ4QzKDvHSg@mail.gmail.com>
	<CAD21AoBT+gx=2V-dKTdrqUeqrnm=6fdJ6r7KFoKNVgLrqDMGsg@mail.gmail.com>
	<CAA4eK1J3Fc0=tE2ZR7XnEfeZm52_4hyQZO1s7kEALFLvZsXxRQ@mail.gmail.com>
	<CAD21AoAZ76=YB_QyQuDNc-NBdGfQ_zbiee3aw7MUVFFmTZPB6A@mail.gmail.com>
	<CAA4eK1JRCQ-bYnbkwUrvcVcbLURjtiW+irFVvXzeG+j=y6jVgA@mail.gmail.com>
	<CAD21AoDR8-sjxrXtQX+ai12kJPR+atM3y5R7ohcj+At6grW7aQ@mail.gmail.com>
	<CAD21AoDOiVPvkcuEDC1cZ=tj67Rh6nErDHmRDAaL7wnqwSYBNQ@mail.gmail.com>
	<CAA4eK1JY=gGysTKdf5uUQSQpe7XVBkYTOWpFLoVZWuEc-rgoAQ@mail.gmail.com>
	<CAD21AoCkisO1b9z44HCdv0FyZBE5FK_nyQg0Y1HJNY1QPGGrRQ@mail.gmail.com>
	<3163a085-66e6-426c-f97b-8df66980c7c4@enterprisedb.com>
	<CAD21AoBh_fRr=pEn6gdazqRVYA5VGXWt4mgmcuFK3iQB8KuTBg@mail.gmail.com>
	<CAA4eK1+BOHXC=0S2kA7GkErWq3-QKj34oQvwAPfuTHq=epf34w@mail.gmail.com>
	<CAD21AoC_AdB5i4OVHu-RWxSFr4nYgcEp2XhVv7i-hpYsX=ANHw@mail.gmail.com>

On 04.10.21 02:31, Masahiko Sawada wrote:
> I guess disabling subscriptions on error/conflict and skipping the
> particular transactions are somewhat different types of functions.
> Disabling subscriptions on error/conflict seems likes a setting
> parameter of subscriptions. The users might want to specify this
> option at creation time. Whereas, skipping the particular transaction
> is a repair function that the user might want to use on the spot in
> case of a failure. I’m concerned a bit that combining these functions
> to one syntax could confuse the users.

Also, would the skip option be dumped and restored using pg_dump?  Maybe 
there is an argument for yes, but if not, then we probably need a 
different path of handling it separate from the more permanent options.





view thread (590+ messages)  latest in thread

Message-ID: <2a9287f4-a870-ee93-d032-b93d7e908ba7@enterprisedb.com>
Permalink:  ../2a9287f4-a870-ee93-d032-b93d7e908ba7@enterprisedb.com/
Also on:    postgresql.org/message-id/2a9287f4-a870-ee93-d032-b93d7e908ba7@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, houzj.fnst@fujitsu.com, tanghy.fnst@fujitsu.com, osumi.takamichi@fujitsu.com, lesovsky@gmail.com, gregn4422@gmail.com
  Subject: Re: Skipping logical replication transactions on subscriber side
  In-Reply-To: <2a9287f4-a870-ee93-d032-b93d7e908ba7@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