Request a Demo
Home   >   mailing lists

Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
Date
Msg-id oxhxaaczgdfywzrkgocow5yrbwva25tx2lx3gns5md7yijyqb7@5fkmgd3i2k4w
Whole thread Raw
In response to Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view 
Hi,

On 2026-01-06 13:35:23 -0500, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > On 2026-01-06 11:40:01 -0500, Tom Lane wrote:
> >> We could either generalize EEOP_PARAM_SET to include an explicit
> >> specification of the source value's address
> 
> > That's pretty trivial, see attached.  I don't quite understand why I didn't go
> > that way immediately...
> 
> Yeah, that looks about right.

Pushed, together with a narrowed down testcase.

Thanks for the report!  Without a reproducer this would have been much much
harder (*).

Greetings,

Andres Freund

* although I do wish we had something like cvise for sql...

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
Next
From: PG Bug reporting form
Date:
Subject: BUG #19372: Scan operator maybe output unnecessary columns to the upper-layer operators