Re: Add a GUC variable that control logical replication - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Add a GUC variable that control logical replication
Date
Msg-id 20191128035334.GO237562@paquier.xyz
Whole thread Raw
In response to Re: Add a GUC variable that control logical replication  (Quan Zongliang <zongliang.quan@postgresdata.com>)
Responses Re: Add a GUC variable that control logical replication  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On Wed, Nov 06, 2019 at 10:01:43PM +0800, Quan Zongliang wrote:
> What the user needs is the same replication link that selectively skips some
> transactions. And this choice only affects transactions that are doing bulk
> delete sessions. The operations of other sessions are not affected and can
> continue to output replication messages.
> For example, session 1 wants to bulk delete 1 million old data from the T1
> table, which can be done without replication. At the same time, session 2
> deletes 10 records from T1, which is expected to be passed on through
> replication.
> Therefore, the two decoders can not meet this requirement. It is also
> inappropriate to temporarily disable subscriptions because it skips all
> transactions for a certain period of time.

Hmm.  The patch discussed on this thread does not have much support
from Peter and Craig, so I am marking it as RwF.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: missing estimation for coalesce function
Next
From: Michael Paquier
Date:
Subject: Re: amcheck verification for GiST