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,
On Tue, Jul 30, 2024 at 7:16 AM Koen De Groote 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 operatio
David,
By "addition" do you mean "adding the table to the publication"? I suppose
that's an option, though I was more thinking about disabling the
publication if an error occurs, similarly to how a subscription is disabled
if "disable_on_error" is set to true, and an error occurs there.
However,
On Tuesday, July 30, 2024, Koen De Groote wrote:
>
> 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.
>
The wording for that option is:
Specifies whether the subscripti
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 wrote:
> Reading this document:
> https://www.postgr
