public inbox for [email protected]  

help / color / mirror / Atom feed
From: Koen De Groote <[email protected]>
To: David G. Johnston <[email protected]>
Cc: PostgreSQL General <[email protected]>
Subject: Re: Understanding conflicts on publications and subscriptions
Date: Wed, 31 Jul 2024 01:22:45 +0200
Message-ID: <CAGbX52F6SUUyENBq=E4rHYgfOnj2KTcgCfS=g9Y=Fna+dWfi_Q@mail.gmail.com> (raw)
In-Reply-To: <CAKFQuwYQB+yCxwEpv7zHekH8y9wmW+Oe+DN2Ly3vZwg=+F5cwA@mail.gmail.com>
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>
	<CAKFQuwYQB+yCxwEpv7zHekH8y9wmW+Oe+DN2Ly3vZwg=+F5cwA@mail.gmail.com>

It indeed seems to be that.

My initial thought of " will be disallowed on those tables" was "on the
subscriber side". After all, why have a publication be of any effect if
there's nobody subscribing to it.

But it appears the publication influences behavior, regardless of there
being a subscriber, which feels counter-intuitive to me.

Thanks for stepping me through it.

On Tue, Jul 30, 2024 at 4:34 PM David G. Johnston <
[email protected]> wrote:

> On Tue, Jul 30, 2024 at 7:16 AM Koen De Groote <[email protected]> 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, for
>> 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.
>
>


view thread (3+ messages)

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], [email protected]
  Subject: Re: Understanding conflicts on publications and subscriptions
  In-Reply-To: <CAGbX52F6SUUyENBq=E4rHYgfOnj2KTcgCfS=g9Y=Fna+dWfi_Q@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