Re: Skipping logical replication transactions on subscriber side - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Skipping logical replication transactions on subscriber side
Date
Msg-id 78a7ef21-bb27-f78a-521e-94ddb4d5c669@enterprisedb.com
Whole thread Raw
In response to Re: Skipping logical replication transactions on subscriber side  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Skipping logical replication transactions on subscriber side
List pgsql-hackers
On 25.01.22 06:18, Amit Kapila wrote:
> I think to avoid this we can send a message to clear this (at least to
> clear XID in the view) after skipping the xact but there is no
> guarantee that it will be received by the stats collector.
> Additionally, the worker can periodically (say after every N (100,
> 500, etc) successful transaction) send a clear message after
> successful apply. This will ensure that eventually the error entry
> will be cleared.

Well, I think we need *some* solution for now.  We can't leave a footgun 
where you say, "skip transaction 700", somehow transaction 700 doesn't 
happen, the whole thing gets forgotten, but then 3 months later, the 
next transaction 700 mysteriously gets dropped.



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Skipping logical replication transactions on subscriber side
Next
From: Dagfinn Ilmari Mannsåker
Date:
Subject: Re: refactoring basebackup.c