| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(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" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Önder Kalacı <onderkalaci(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | RE: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL |
| Date: | 2023-07-11 07:04:29 |
| Message-ID: | TYAPR01MB5866587BAD92EFC56E98E01BF531A@TYAPR01MB5866.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Sergei,
Thank you for giving comment!
The restriction is only for subscriber: the publisher can publish the changes
to downstream under the condition, but the subscriber cannot apply that.
> So, I suggest to mention subscriber explicitly:
>
> + class of Btree, then <literal>UPDATE</literal> and
> <literal>DELETE</literal>
> - operations cannot be replicated.
> + operations cannot be applied on subscriber.
I accepted the comment. Please see [1].
Best Regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jakub Wartak | 2023-07-11 07:09:43 | Re: Performance degradation on concurrent COPY into a single relation in PG16. |
| Previous Message | Hayato Kuroda (Fujitsu) | 2023-07-11 07:00:03 | RE: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL |