MIME-Version: 1.0
References: <CAGbX52FFehm9PnRef5_KeAwbUqxr6-6PprVCpUhORb5nH1txQg@mail.gmail.com>
In-Reply-To: <CAGbX52FFehm9PnRef5_KeAwbUqxr6-6PprVCpUhORb5nH1txQg@mail.gmail.com>
From: Koen De Groote <kdg.dev@gmail.com>
Date: Tue, 30 Jul 2024 15:52:23 +0200
Message-ID: <CAGbX52FGYVfXStV0Z7jPokCE_CpFEDahZAS1CqLg_9qwHke4dA@mail.gmail.com>
Subject: Re: Understanding conflicts on publications and subscriptions
To: PostgreSQL General <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000359dc3061e774a57"
Archived-At: <https://www.postgresql.org/message-id/CAGbX52FGYVfXStV0Z7jPokCE_CpFEDahZAS1CqLg_9qwHke4dA%40mail.gmail.com>
Precedence: bulk

--000000000000359dc3061e774a57
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFPM Koen De Groote <kdg.dev@gmail.com> =
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 o=
perations
> 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 fo=
r
> 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.
>

--000000000000359dc3061e774a57
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Just to add a thought:</div><div><br></div><div>If th=
e subscriber gets a bit of logic to say &quot;Something went wrong, so I=
9;m automatically stopping what I&#39;m doing&quot;, it sounds logical to g=
ive the publisher the same ability.<br></div></div><br><div class=3D"gmail_=
quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 30, 2024 at 3:47=
=E2=80=AFPM Koen De Groote &lt;<a href=3D"mailto:kdg.dev@gmail.com">kdg.dev=
@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr"><div>Reading this document: <a href=3D"https://=
www.postgresql.org/docs/16/logical-replication-conflicts.html" target=3D"_b=
lank">https://www.postgresql.org/docs/16/logical-replication-conflicts.html=
</a></div><div><br></div><div>There is talk of the &quot;disable_on_error&q=
uot; option when creating a subscription.</div><div><br></div><div>The conf=
licts this applies to, I am assuming are only conflicts caused on the side =
of the subscription?</div><div><br></div><div>As an attempt to apply new da=
ta doesn&#39;t work, because of modifications made since the initial copy, =
is that correct?</div><div><br></div><div><br></div><div>I&#39;m a bit conf=
used by errors on the side of the publisher. Reading this document: <a href=
=3D"https://www.postgresql.org/docs/16/sql-createpublication.html" target=
=3D"_blank">https://www.postgresql.org/docs/16/sql-createpublication.html</=
a></div><div><br></div><div>It states:</div><div><br></div><div>&gt; The ta=
bles added to a publication that publishes<span>=C2=A0</span><code style=3D=
"box-sizing:border-box;font-family:monospace,monospace;font-size:1em;border=
-radius:0.25rem;margin:0.6rem 0px;font-weight:400">UPDATE</code><span>=C2=
=A0</span>and/or<span>=C2=A0</span><code style=3D"box-sizing:border-box;fon=
t-family:monospace,monospace;font-size:1em;border-radius:0.25rem;margin:0.6=
rem 0px;font-weight:400">DELETE</code><span>=C2=A0</span>operations must ha=
ve<span>=C2=A0</span><code style=3D"box-sizing:border-box;font-family:monos=
pace,monospace;font-size:1em;border-radius:0.25rem;margin:0.6rem 0px;font-w=
eight:400">REPLICA IDENTITY</code><span>=C2=A0</span>defined. Otherwise tho=
se operations will be disallowed on those tables.</div><div><br></div><div>=
This is not related to the subscription option &quot;disable_on_error&quot;=
, I take it?</div><div><br></div><div>Because it sure would be nice if ther=
e was a way to do a similar thing for the subscription, disabling it on err=
or.</div><div><br></div><div>Am I getting this right? &quot;disable_on_erro=
r&quot; is only on subscription, and errors on the publishers related to re=
plica identity are not tied to that?</div><div><br></div><div>Thanks for yo=
ur time.</div></div>
</blockquote></div>

--000000000000359dc3061e774a57--