Re: Optionally automatically disable logical replication subscriptions on error

[Mark Dilger]

> On Jun 20, 2021, at 8:09 PM, Amit Kapila <amit.kapil...@gmail.com> wrote:
> 
> Because currently, we don't proceed after an error unless it is
> resolved. Why do you think there could be multiple such transactions?

Just as one example, if the subscriber has a unique index that the publisher 
lacks, any number of transactions could add non-unique data that then fails to 
apply on the subscriber.  My patch took the view that the user should figure 
out how to get the subscriber side consistent with the publisher side, but if 
you instead take the approach that problematic commits should be skipped, it 
would seem that arbitrarily many such transactions could be committed on the 
publisher side.

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company