From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: David Rowley <dgrowleyml@gmail.com>
Cc: redraiment@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
Date: Tue, 06 Jan 2026 13:35:23 -0500
Message-ID: <1606057.1767724523@sss.pgh.pa.us> (raw)
In-Reply-To: <x7asrlzgreocucl4z3wdwt6ve526z35tobwao6omnbhkhsywyb@525iqsuva2v5>
References: <19370-7fb7a5854b7618f1@postgresql.org>
<CAApHDvpVwUTNEQKkBVD9CQCq6N+YW7hpH6C3ZtKJQnGX4XAtpA@mail.gmail.com>
<1588384.1767715181@sss.pgh.pa.us>
<1593905.1767717601@sss.pgh.pa.us>
<x7asrlzgreocucl4z3wdwt6ve526z35tobwao6omnbhkhsywyb@525iqsuva2v5>
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.
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, dgrowleyml@gmail.com, redraiment@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
In-Reply-To: <1606057.1767724523@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox