MIME-Version: 1.0
References: <19434-297bf2cbd8d2931a@postgresql.org>
In-Reply-To: <19434-297bf2cbd8d2931a@postgresql.org>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Mon, 23 Mar 2026 12:47:06 -0400
Message-ID: <CAKAnmm+csbrmkn5SFUd60SAAfe9P1+srbjuEPWvH+3XNCvDrwA@mail.gmail.com>
Subject: Re: BUG #19434: adding WHERE to a publication can cause UPDATEs and
 DELETEs to fail on the source table
To: tim@gotab.io, pgsql-bugs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000081f6f064db3cb97"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmm%2Bcsbrmkn5SFUd60SAAfe9P1%2BsrbjuEPWvH%2B3XNCvDrwA%40mail.gmail.com>
Precedence: bulk

--000000000000081f6f064db3cb97
Content-Type: text/plain; charset="UTF-8"

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

--000000000000081f6f064db3cb97
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I don&#39;t think this is really a bug, more of a feature =
request / optimization. However, I do agree this is an important one. I don=
&#39;t see offhand why we can&#39;t append the where list to our existing l=
ist of important columns. There would be a few downsides, but none that wou=
ld be worse than going full replica identity or creating a new index. I&#39=
;ll see about making a proof of concept patch and throwing it on -hackers. =
Will cc you on that.<div><br></div><div>Cheers,</div><div>Greg</div><div><b=
r></div></div>

--000000000000081f6f064db3cb97--