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

From: Sergei Kornilov <sk(at)zsrv(dot)org>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Peter Smith <smithpb2250(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Önder Kalacı <onderkalaci(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Subject: Re:doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL
Date: 2023-07-10 11:03:19
Message-ID: 167011688986999@66nstrt5m7cueoi3.vla.yp-c.yandex.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kumar, Sachin 2023-07-10 11:06:04 RE: Initial Schema Sync for Logical Replication
Previous Message Heikki Linnakangas 2023-07-10 10:50:59 Re: optimize several list functions with SIMD intrinsics