If the subscriber gets a bit of logic to say "Something went wrong, so I'm automatically stopping what I'm doing", it sounds logical to give the publisher the same ability.
On Tue, Jul 30, 2024 at 3:47 PM Koen De Groote <kdg.dev@gmail.com> wrote:
> The tables added to a publication that publishesUPDATEand/orDELETEoperations must haveREPLICA IDENTITYdefined. 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?