On Mon, 7 Sept 2026 at 23:52, Andrei Lepikhov <[email protected]> wrote:
>
> On 07/09/2026 10:25, Andrei Lepikhov wrote:
> > Removed. Adding a regression test alongside a bug fix is just my default 
> > habit,
> > so I followed it here without thinking it through - happy to drop them.
> It looks like I mistakenly sent the old version as v2. Here is the actual
> version (v3) of the patch.

I was thinking that this might only be worth fixing on master. I'd say
it's increasingly likely as we make the software faster and computers
get faster, plus more efficient tableAMs, will result in overflows
being more likely in the future. That might mean it's inevitable that
we will need to fix it at some point.

The concern I have with backpatching is around the new
PG_RETURN_INPUT() macro. That existing in backbranches but not all
minor versions of the given release could lead to any extension that
opts to use the macro not compiling on older minor versions that don't
have the macro defined.

Any other ideas?

David


Reply via email to