| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com>, 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> |
| Subject: | RE: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL |
| Date: | 2023-07-14 08:45:43 |
| Message-ID: | TYCPR01MB58705C01D3AAF1740D58E8E5F534A@TYCPR01MB5870.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Amit, Sergei,
> > I think it's appropriate to add on the restrictions page. (But mentioning that this
> restriction is only for subscriber)
> >
> > If the list were larger, then the restrictions page could be divided into publisher
> and subscriber restrictions. But not for one very specific restriction.
> >
>
> Okay, how about something like: "The UPDATE and DELETE operations
> cannot be applied on the subscriber for the published tables that
> specify REPLICA IDENTITY FULL when the table has attributes with
> datatypes (e.g point or box) that don't have a default operator class
> for Btree or Hash. This won't be a problem if the table has a primary
> key or replica identity defined for it."?
Thanks for discussing and giving suggestions. But it seems that the first
sentence is difficult to read for me. How about attached?
Best Regards,
Hayato Kuroda
FUJITSU LIMITED
| Attachment | Content-Type | Size |
|---|---|---|
| v4_add_description.patch | application/octet-stream | 1.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2023-07-14 08:55:28 | Re: MERGE ... RETURNING |
| Previous Message | Daniel Gustafsson | 2023-07-14 08:35:42 | Re: DROP DATABASE is interruptible |