There is talk of the "disable_on_error" option when creating a subscription.
The conflicts this applies to, I am assuming are only conflicts caused on the side of the subscription?
As an attempt to apply new data doesn't work, because of modifications made since the initial copy, is that correct?
It states:
> The tables added to a publication that publishes UPDATE
and/or DELETE
operations must have REPLICA IDENTITY
defined. Otherwise those operations will be disallowed on those tables.
This is not related to the subscription option "disable_on_error", I take it?
Because it sure would be nice if there was a way to do a similar thing for the subscription, disabling it on error.
Am I getting this right? "disable_on_error" is only on subscription, and errors on the publishers related to replica identity are not tied to that?
Thanks for your time.