MIME-Version: 1.0
References: <CAGbX52FFehm9PnRef5_KeAwbUqxr6-6PprVCpUhORb5nH1txQg@mail.gmail.com>
 <CAGbX52FGYVfXStV0Z7jPokCE_CpFEDahZAS1CqLg_9qwHke4dA@mail.gmail.com>
 <CAKFQuwY1Fs0-a_wPidhcbdC2o503bBAVjXdbLN-QozC5HMqATA@mail.gmail.com> <CAGbX52Hk4vSiB0FkvOv9z+U8T72cHwD7o+kF_tfdtm=m4UYQiQ@mail.gmail.com>
In-Reply-To: <CAGbX52Hk4vSiB0FkvOv9z+U8T72cHwD7o+kF_tfdtm=m4UYQiQ@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Tue, 30 Jul 2024 07:33:37 -0700
Message-ID: <CAKFQuwYQB+yCxwEpv7zHekH8y9wmW+Oe+DN2Ly3vZwg=+F5cwA@mail.gmail.com>
Subject: Re: Understanding conflicts on publications and subscriptions
To: Koen De Groote <kdg.dev@gmail.com>
Cc: PostgreSQL General <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000287d4a061e77df1c"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwYQB%2ByCxwEpv7zHekH8y9wmW%2BOe%2BDN2Ly3vZwg%3D%2BF5cwA%40mail.gmail.com>
Precedence: bulk

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

On Tue, Jul 30, 2024 at 7:16=E2=80=AFAM Koen De Groote <kdg.dev@gmail.com> =
wrote:

>  And if my understanding is correct: if a table doesn't have a replica
> identity, any UPDATE or DELETE statement that happens on the publisher, f=
or
> that table, will be refused.
>
>
That is how I read the sentence "Otherwise those operations will be
disallowed on those tables."

Upon adding said table to a publication, future attempts to run updates and
deletes will result in failures in the transactions performing said DML.

Feel free to experiment that the behavior indeed matches the wording in the
documentation.

David J.

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

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif"><span style=3D"font-family:Arial,Helve=
tica,sans-serif">On Tue, Jul 30, 2024 at 7:16=E2=80=AFAM Koen De Groote &lt=
;<a href=3D"mailto:kdg.dev@gmail.com">kdg.dev@gmail.com</a>&gt; wrote:</spa=
n><br></div></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"ltr"><div>=C2=A0And if my understanding is =
correct: if a table doesn&#39;t have a replica identity, any UPDATE or DELE=
TE statement that happens on the publisher, for that table, will be refused=
.<br></div><div><br></div></div></blockquote><div><br></div><div class=3D"g=
mail_default" style=3D"font-family:arial,helvetica,sans-serif">That is how =
I read the sentence &quot;Otherwise those operations will be disallowed on =
those tables.&quot;</div><div class=3D"gmail_default" style=3D"font-family:=
arial,helvetica,sans-serif"><br></div><div class=3D"gmail_default" style=3D=
"font-family:arial,helvetica,sans-serif">Upon adding said table to a public=
ation, future attempts to run updates and deletes will result in failures i=
n the transactions performing said DML.</div><div class=3D"gmail_default" s=
tyle=3D"font-family:arial,helvetica,sans-serif"><br></div><div class=3D"gma=
il_default" style=3D"font-family:arial,helvetica,sans-serif">Feel free to e=
xperiment that the behavior indeed matches the wording in the documentation=
.</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sa=
ns-serif"><br></div><div class=3D"gmail_default" style=3D"font-family:arial=
,helvetica,sans-serif">David J.</div><div class=3D"gmail_default" style=3D"=
font-family:arial,helvetica,sans-serif"><br></div></div></div>

--000000000000287d4a061e77df1c--