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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ocean_li_996(at)163(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17236: Postgres core on pstate->p_multiassign_exprs
Date: 2021-10-19 15:38:21
Message-ID: 1816445.1634657901@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-10-19 16:33:17 BUG #17238: Link to "Using EXPLAIN" in the "EXPLAIN" documentation
Previous Message Bossart, Nathan 2021-10-19 14:40:04 Re: BUG #17220: ALTER INDEX ALTER COLUMN SET (..) with an optionless opclass makes index and table unusable