From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: ignestid@gmail.com
Subject: BUG #18319: Logical Replication updates causing duplication of row if evaluation filter is set to the same field
Date: Wed, 31 Jan 2024 15:42:34 +0000
Message-ID: <18319-2fa5e804b55eb54d@postgresql.org> (raw)
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-...
) , 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, ignestid@gmail.com
Subject: Re: BUG #18319: Logical Replication updates causing duplication of row if evaluation filter is set to the same field
In-Reply-To: <18319-2fa5e804b55eb54d@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox