| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, krking(at)zju(dot)edu(dot)cn, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17477: A crash bug in transformValuesClause() |
| Date: | 2022-05-09 18:33:38 |
| Message-ID: | 3910641.1652121218@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> writes:
> On Tue, May 10, 2022 at 2:20 AM Jonathan S. Katz <jkatz(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2022-05-09 20:55:06 | Re: BUG #17477: A crash bug in transformValuesClause() |
| Previous Message | Masahiko Sawada | 2022-05-09 18:15:04 | Re: BUG #17477: A crash bug in transformValuesClause() |