Re: BUG #19434: adding WHERE to a publication can cause UPDATEs and DELETEs to fail on the source table

From: Tim McLaughlin <tim(at)gotab(dot)io>
To: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19434: adding WHERE to a publication can cause UPDATEs and DELETEs to fail on the source table
Date: 2026-03-23 19:49:22
Message-ID: CAA6J38J6S8k2gixxGJ9C_VfXKRdTdsRJJpWFqpLMeqqHFtvE8w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks for the feedback, Greg.

Cheers,
Tim
+1-571-263-1023

On Mon, Mar 23, 2026 at 12:47 PM Greg Sabino Mullane <htamfids(at)gmail(dot)com>
wrote:

> I don't think this is really a bug, more of a feature request /
> optimization. However, I do agree this is an important one. I don't see
> offhand why we can't append the where list to our existing list of
> important columns. There would be a few downsides, but none that would be
> worse than going full replica identity or creating a new index. I'll see
> about making a proof of concept patch and throwing it on -hackers. Will cc
> you on that.
>
> Cheers,
> Greg
>
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Korotkov 2026-03-23 21:28:45 Re: BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
Previous Message Greg Sabino Mullane 2026-03-23 16:47:06 Re: BUG #19434: adding WHERE to a publication can cause UPDATEs and DELETEs to fail on the source table