|From:||Michael Paquier <michael(at)paquier(dot)xyz>|
|To:||Quan Zongliang <zongliang(dot)quan(at)postgresdata(dot)com>|
|Cc:||Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Add a GUC variable that control logical replication|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
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
> 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.
|Next Message||Michael Paquier||2019-11-28 03:57:10||Re: amcheck verification for GiST|
|Previous Message||Pavel Stehule||2019-11-28 03:48:54||Re: missing estimation for coalesce function|