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

--000000000000019e46061e7738f1
Content-Type: text/plain; charset="UTF-8"

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.

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

<div dir=3D"ltr"><div>Reading this document: <a href=3D"https://www.postgre=
sql.org/docs/16/logical-replication-conflicts.html">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&quot; option when creating a s=
ubscription.</div><div><br></div><div>The conflicts this applies to, I am a=
ssuming are only conflicts caused on the side of the subscription?</div><di=
v><br></div><div>As an attempt to apply new data doesn&#39;t work, because =
of modifications made since the initial copy, is that correct?</div><div><b=
r></div><div><br></div><div>I&#39;m a bit confused by errors on the side of=
 the publisher. Reading this document: <a href=3D"https://www.postgresql.or=
g/docs/16/sql-createpublication.html">https://www.postgresql.org/docs/16/sq=
l-createpublication.html</a></div><div><br></div><div>It states:</div><div>=
<br></div><div>&gt; The tables added to a publication that publishes<span>=
=C2=A0</span><code class=3D"gmail-command" style=3D"box-sizing:border-box;f=
ont-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 class=3D"gmail-command" style=3D"box-sizing:border-box;font=
-family:monospace,monospace;font-size:1em;border-radius:0.25rem;margin:0.6r=
em 0px;font-weight:400">DELETE</code><span>=C2=A0</span>operations must hav=
e<span>=C2=A0</span><code class=3D"gmail-literal" style=3D"box-sizing:borde=
r-box;font-family:monospace,monospace;font-size:1em;border-radius:0.25rem;m=
argin:0.6rem 0px;font-weight:400">REPLICA IDENTITY</code><span>=C2=A0</span=
>defined. Otherwise those operations will be disallowed on those tables.</d=
iv><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 sur=
e would be nice if there was a way to do a similar thing for the subscripti=
on, disabling it on error.</div><div><br></div><div>Am I getting this right=
? &quot;disable_on_error&quot; is only on subscription, and errors on the p=
ublishers related to replica identity are not tied to that?</div><div><br><=
/div><div>Thanks for your time.</div></div>

--000000000000019e46061e7738f1--