Re: BUG #17477: A crash bug in transformValuesClause() - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17477: A crash bug in transformValuesClause()
Date
Msg-id 3910641.1652121218@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #17477: A crash bug in transformValuesClause()  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-bugs
Masahiko Sawada <sawada.mshk@gmail.com> writes:
> On Tue, May 10, 2022 at 2:20 AM Jonathan S. Katz <jkatz@postgresql.org> wrote:
>> Confirmed reproducing the crash and that this fixes it. I did a short
>> double-take on the error message:
>>
>> ERROR:  subquery must return only one column
>>
>> but it is accurate, given this is what the subquery must do, and zero !=
>> one.

> Agreed. I've also confirmed that the patch fixes this issue and passed
> the regression tests.

Thanks for checking!  I've pushed the fix now.

When we have a little more time, we might want to look into making
VALUES-with-no-columns be fully supported, that is not a syntax error.
That's not a crasher bug though, so I feel no desire to deal with
it under a release deadline.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: BUG #17477: A crash bug in transformValuesClause()
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #17477: A crash bug in transformValuesClause()