Horton

RE: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL

Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>

View thread
From: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
To: 'Peter Smith' <smithpb2250@gmail.com>
Cc: "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>, Amit Kapila <amit.kapila16@gmail.com>, Önder Kalacı <onderkalaci@gmail.com>
Date: 2023-07-10T09:03:16Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Doc: Update the logical replication restriction w.r.t Replica Identity Full.

Attachments

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