From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: luy70@psu.edu
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18877: PostgreSQL triggers assertion failure
Date: Sat, 05 Apr 2025 11:12:59 -0400
Message-ID: <2461845.1743865979@sss.pgh.pa.us> (raw)
In-Reply-To: <202504051500.v6ekizm5fcv4@alvherre.pgsql>
References: <202504051500.v6ekizm5fcv4@alvherre.pgsql>
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> On 2025-Apr-05, Tom Lane wrote:
>> So what we should be doing is building a parse-analysis result
>> that deparses into something that looks like the input; probably,
>> a JsonArrayQueryConstructor node with an analyzed EXPR_SUBLINK
>> SubLink below it. Then we can make this tlist-length check against
>> the analyzed SubLink, removing the problem of premature errors that
>> are not spelled the way we want.
> Sounds reasonable, I can try to find better coding for this, but it
> won't be soon. I won't be sad if somebody else wants to do it, so if
> you feel like it, please be my guest.
Yeah, it's not high priority for me either. Maybe someone else
will be interested in the project.
>> Anyway, that idea is far too invasive to be back-patchable,
>> and IMO it's too late to consider even getting it into v18.
>> So what I'm thinking is we should just apply the copyObject
>> hack for now, and resolve to reconsider this code later.
> Sounds reasonable.
OK, I'll get that done.
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, alvherre@alvh.no-ip.org, luy70@psu.edu, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18877: PostgreSQL triggers assertion failure
In-Reply-To: <2461845.1743865979@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