pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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
Date: Tue, 19 Oct 2021 11:38:21 -0400
Message-ID: <1816445.1634657901@sss.pgh.pa.us> (raw)
In-Reply-To: <17236-3210de9bcba1d7ca@postgresql.org>
References: <17236-3210de9bcba1d7ca@postgresql.org>

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





view thread (3+ messages)

Message-ID: <1816445.1634657901@sss.pgh.pa.us>
Permalink:  ../1816445.1634657901@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1816445.1634657901@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, ocean_li_996@163.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #17236: Postgres core on pstate->p_multiassign_exprs
  In-Reply-To: <1816445.1634657901@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox