From: Tom Lane <tgl@sss.pgh.pa.us>
To: ocean_li_996@163.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17236: Postgres core on pstate->p_multiassign_exprs
In-reply-to: <17236-3210de9bcba1d7ca@postgresql.org>
References: <17236-3210de9bcba1d7ca@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 18 Oct 2021 11:20:14 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1816444.1634657901.1@sss.pgh.pa.us>
Date: Tue, 19 Oct 2021 11:38:21 -0400
Message-ID: <1816445.1634657901@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1816445.1634657901%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Postgres will crash when executing the following SQL:
> CREATE TABLE v0 ( v1 INT , v2 INT ) ; 
> UPDATE v0 SET ( v1 , v2 ) = ( SELECT v2 + 127 , v1 FROM v0 ) , v2 = ( v2 ,
> v1 ) , v1 = 53 , v2 = 54 ;

After further reflection, this assertion is just wrong, and we
should remove it, as I've now done.  The lack of previous field
reports doubtless stems from the fact that most users don't
use assert-enabled builds, so there was no bug for them.

Thanks for the report!

			regards, tom lane