public inbox for [email protected]
help / color / mirror / Atom feedFrom: Koen De Groote <[email protected]>
To: PostgreSQL General <[email protected]>
Subject: Re: Understanding conflicts on publications and subscriptions
Date: Tue, 30 Jul 2024 15:52:23 +0200
Message-ID: <CAGbX52FGYVfXStV0Z7jPokCE_CpFEDahZAS1CqLg_9qwHke4dA@mail.gmail.com> (raw)
In-Reply-To: <CAGbX52FFehm9PnRef5_KeAwbUqxr6-6PprVCpUhORb5nH1txQg@mail.gmail.com>
References: <CAGbX52FFehm9PnRef5_KeAwbUqxr6-6PprVCpUhORb5nH1txQg@mail.gmail.com>
Just to add a thought:
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 <[email protected]> wrote:
> Reading this document:
> https://www.postgresql.org/docs/16/logical-replication-conflicts.html
>
> 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?
>
>
> I'm a bit confused by errors on the side of the publisher. Reading this
> document: https://www.postgresql.org/docs/16/sql-createpublication.html
>
> 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.
>
view thread (2+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Understanding conflicts on publications and subscriptions
In-Reply-To: <CAGbX52FGYVfXStV0Z7jPokCE_CpFEDahZAS1CqLg_9qwHke4dA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox