| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Peter Smith' <smithpb2250(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Önder Kalacı <onderkalaci(at)gmail(dot)com> |
| Subject: | RE: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL |
| Date: | 2023-07-10 09:03:16 |
| Message-ID: | TYAPR01MB586607EB47374B7D5C595B0CF530A@TYAPR01MB5866.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Peter,
Thanks for checking! PSA new version.
> 1.
> SUGGESTION (minor reword)
> If the published table specifies <literal>REPLICA IDENTITY
> FULL</literal> but the table includes an attribute whose datatype is
> not an operator class of Btree, then <literal>UPDATE</literal> and
> <literal>DELETE</literal> operations cannot be replicated. To make it
> work, a primary key should be defined on the subscriber table, or a
> different appropriate replica identity must be specified.
Seems better, fixed.
> 2.
> Maybe "REPLICA IDENTITY FULL" should have a link, like from this [1] page.
Added.
Best Regards,
Hayato Kuroda
FUJITSU LIMITED
| Attachment | Content-Type | Size |
|---|---|---|
| v2_add_description.patch | application/octet-stream | 990 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2023-07-10 09:08:35 | Re: RADIUS tests and improvements |
| Previous Message | Alena Rybakina | 2023-07-10 08:38:17 | Re: POC, WIP: OR-clause support for indexes |