| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Sergei Kornilov <sk(at)zsrv(dot)org> |
| Cc: | Peter Smith <smithpb2250(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Önder Kalacı <onderkalaci(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Subject: | Re: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL |
| Date: | 2023-07-10 12:46:28 |
| Message-ID: | CAA4eK1+iJN9hzyBr3OAYmhsHmUkLmoCb0swEATSEKyPTJzcxzQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 10, 2023 at 4:33 PM Sergei Kornilov <sk(at)zsrv(dot)org> wrote:
>
> Is this restriction only for the subscriber?
>
> If we have not changed the replica identity and there is no primary key, then we forbid update and delete on the publication side (a fairly common usage error at the beginning of using publications).
> If we have replica identity FULL (the table has such a column), then on the subscription side, update and delete will be performed.
>
In the above sentence, do you mean the publisher side?
>
But we will not be able to apply them on a subscription. Right?
>
If your previous sentence talks about the publisher and this sentence
about the subscriber then what you are saying is correct. You can see
the example in the email [1].
> This is an important difference for real use, when the subscriber is not necessarily postgresql - for example, debezium.
>
Can you explain the difference and problem you are seeing? As per my
understanding, this is the behavior from the time logical replication
has been introduced.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2023-07-10 12:50:18 | Re: [PATCH] Infinite loop while acquiring new TOAST Oid |
| Previous Message | Daniel Gustafsson | 2023-07-10 12:44:31 | Re: [PATCH] Slight improvement of worker_spi.c example |