| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| 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-06 18:35:23 |
| Message-ID: | 1606057.1767724523@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
> At the very least we need to create a simplified testcase for the bug at hand.
Yup, the sudoku example is fun but it seems inappropriate as a test
case.
>> or insert some kind of LOAD operation to copy the computed value into
>> state->resvalue/resnull. I don't see anything that looks like that today,
>> though.
> Hm, wouldn't that have exactly the same issues as we have today anyway?
Indeed ... -ENOCAFFEINE
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next 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 |
| Previous Message | Andres Freund | 2026-01-06 17:42:56 | Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression |