Horton

Re: BUG #17236: Postgres core on pstate->p_multiassign_exprs

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: ocean_li_996@163.com
Cc: pgsql-bugs@lists.postgresql.org
Date: 2021-10-19T15:38:21Z
Lists: pgsql-bugs 
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

Commits

  1. Remove bogus assertion in transformExpressionList().

  2. Fix portability issues in new TAP tests of psql