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

From Sergei Kornilov
Subject Re:doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL
Date
Msg-id 167011688986999@66nstrt5m7cueoi3.vla.yp-c.yandex.net
Whole thread Raw
In response to Re: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL
List 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
publicationside (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
beperformed. 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



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: optimize several list functions with SIMD intrinsics
Next
From: "Kumar, Sachin"
Date:
Subject: RE: Initial Schema Sync for Logical Replication