From: Alexander Lakhin <exclusion@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array
Date: Sun, 30 Apr 2023 07:00:00 +0300
Message-ID: <a8dfc214-5445-147e-2ebc-4de43ed56d38@gmail.com> (raw)
In-Reply-To: <1805878.1682788590@sss.pgh.pa.us>
References: <17912-82ceed78731d9cdc@postgresql.org>
<1392974.1682694846@sss.pgh.pa.us>
<bf33fe9b-f2f8-5885-aae3-537cd4591386@gmail.com>
<1440309.1682705916@sss.pgh.pa.us>
<1483429.1682709429@sss.pgh.pa.us>
<5ebae5e4-d401-fadf-8585-ac3eaf53219c@gmail.com>
<1805878.1682788590@sss.pgh.pa.us>
29.04.2023 20:16, Tom Lane wrote:
>> I suppose that waiting for v17 is preferable if the patch is considered as
>> bringing a new feature (it's not the case) or could require extra time to
>> stabilize. But I'm afraid that anomalies, that would require additional
>> fixes for the change stabilization, could be related to the existing
>> code, and thus that extra time will be invested in improving v16- too.
> I'm a little uncomfortable with changing the semantics of non-failing
> cases in the back branches.
I agree that we shouldn't introduce a new behavior in the released branches.
For that moment I was thinking about the choice between v16 and v17
for that patch to be committed to.
But as you see the better solution now, the patch will be different and more
extensive, I suppose, so I'd vote for postponing it for v17.
Best regards,
Alexander
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: exclusion@gmail.com, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array
In-Reply-To: <a8dfc214-5445-147e-2ebc-4de43ed56d38@gmail.com>
* 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