Re: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL
Date
Msg-id CAA4eK1JQmZGkJESGyi14eD0ySnFjGtbXiHYaJ+cx6v1n3AdGkg@mail.gmail.com
Whole thread Raw
In response to RE: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
Responses Re:doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL
RE: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL
List pgsql-hackers
On Mon, Jul 10, 2023 at 2:33 PM Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:
>

     If the published table specifies
+     <link linkend="sql-altertable-replica-identity-full"><literal>REPLICA
IDENTITY FULL</literal></link>
+     but the table includes an attribute whose datatype is not an operator
+     class of Btree,

Isn't the same true for the hash operator class family as well? Can we
slightly change the line as: "... the table includes an attribute
whose datatype doesn't have an equality operator defined for it..".
Also, I find the proposed wording a bit odd, can we swap the sentence
to say something like: "The UPDATE and DELETE operations cannot be
replicated for the published tables that specifies REPLICA IDENTITY
FULL but the table includes an attribute whose datatype doesn't have
an equality operator defined for it on the subscriber."?

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Request for comment on setting binary format output per session
Next
From: Matthias van de Meent
Date:
Subject: Re: PATCH: Using BRIN indexes for sorted output