BUG #18319: Logical Replication updates causing duplication of row if evaluation filter is set to the same field - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #18319: Logical Replication updates causing duplication of row if evaluation filter is set to the same field
Date
Msg-id 18319-2fa5e804b55eb54d@postgresql.org
Whole thread Raw
Responses Re: BUG #18319: Logical Replication updates causing duplication of row if evaluation filter is set to the same field  (Peter Smith <smithpb2250@gmail.com>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      18319
Logged by:          Daniele Ignesti
Email address:      ignestid@gmail.com
PostgreSQL version: 15.5
Operating system:   OEL 8.8
Description:

Good Morning,

i'm facing the following issue:
i have a publication (pub1) with publish of insert and update transactions
made on table tab1 .
if i update tab1 with the following statement:

update tab1 set field1 = 'value2' where field1='value1';

logical decoding on subscriber process read the transaction , and following
the guidelines of  "31.3.3. UPDATE Transformations"  (

https://www.postgresql.org/docs/current/logical-replication-row-filter.html#LOGICAL-REPLICATION-ROW-FILTER-TRANSFORMATIONS
) , the subscriber try as first thing the delete of old row and then the
insert of the new row .

What i think is a bug ,  is that the delete on old row is never done unless
you specify publishing deletes on publications.
So not all updates are published on subscriber unless you explicitily set
publish deletes on publisher.

Regards,

Daniele


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18318: Different character codes are mixed in the log file in Japanese locale.
Next
From: Laurenz Albe
Date:
Subject: Re: Cascade rules on INSERT wrong behaviour on 16.0