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

Sergei Kornilov <sk@zsrv.org>

From: Sergei Kornilov <sk@zsrv.org>

To: Amit Kapila <amit.kapila16@gmail.com>

Cc: Peter Smith <smithpb2250@gmail.com>, pgsql-hackers@lists.postgresql.org, Önder Kalacı <onderkalaci@gmail.com>, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>

Date: 2023-07-10T11:03:19Z

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 →

Doc: Update the logical replication restriction w.r.t Replica Identity Full.
- 961cf5c9055f 17.0 landed

Hello

Is this restriction only for the subscriber?

If we have not changed the replica identity and there is no primary key, then we forbid update and delete on the publication side (a fairly common usage error at the beginning of using publications).
If we have replica identity FULL (the table has such a column), then on the subscription side, update and delete will be performed. But we will not be able to apply them on a subscription. Right?

This is an important difference for real use, when the subscriber is not necessarily postgresql - for example, debezium.

regards, Sergei