Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1no8CX-0007hf-NA for pgsql-bugs@arkaria.postgresql.org; Mon, 09 May 2022 18:33:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1no8CW-0007S7-9s for pgsql-bugs@arkaria.postgresql.org; Mon, 09 May 2022 18:33:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1no8CW-0007Ry-1Y for pgsql-bugs@lists.postgresql.org; Mon, 09 May 2022 18:33:44 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1no8CT-0007BJ-Mf; Mon, 09 May 2022 18:33:43 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 249IXcrw3910642; Mon, 9 May 2022 14:33:38 -0400 From: Tom Lane To: Masahiko Sawada cc: "Jonathan S. Katz" , krking@zju.edu.cn, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17477: A crash bug in transformValuesClause() In-reply-to: References: <17477-0af3c6ac6b0a6ae0@postgresql.org> <3809468.1652109938@sss.pgh.pa.us> <6f7f0d34-0f58-41a9-98b5-bf86e1960165@postgresql.org> Comments: In-reply-to Masahiko Sawada message dated "Tue, 10 May 2022 03:15:04 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3910640.1652121218.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 09 May 2022 14:33:38 -0400 Message-ID: <3910641.1652121218@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Masahiko Sawada writes: > On Tue, May 10, 2022 at 2:20 AM Jonathan S. Katz = 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 != =3D >> 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