Re: Optionally automatically disable logical replication subscriptions on error

> On Jun 20, 2021, at 8:09 PM, Amit Kapila <amit.kapila16@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
addnon-unique data that then fails to apply on the subscriber.  My patch took the view that the user should figure out
howto get the subscriber side consistent with the publisher side, but if you instead take the approach that problematic
commitsshould 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