| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, redraiment(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression |
| Date: | 2026-01-07 01:04:15 |
| Message-ID: | oxhxaaczgdfywzrkgocow5yrbwva25tx2lx3gns5md7yijyqb7@5fkmgd3i2k4w |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On 2026-01-06 13:35:23 -0500, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)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...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2026-01-07 08:11:02 | BUG #19372: Scan operator maybe output unnecessary columns to the upper-layer operators |
| Previous Message | Tom Lane | 2026-01-06 19:01:33 | Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression |