Re: pgsql: Allow a multi-row INSERT to specify DEFAULTs for a generated col - Mailing list pgsql-committers

From Laurenz Albe
Subject Re: pgsql: Allow a multi-row INSERT to specify DEFAULTs for a generated col
Date
Msg-id 6906fe3025b8a8fc7a3c1f120b93726db53c7ed3.camel@cybertec.at
Whole thread Raw
In response to pgsql: Allow a multi-row INSERT to specify DEFAULTs for a generated col  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Allow a multi-row INSERT to specify DEFAULTs for a generated col  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On Sun, 2020-11-22 at 20:48 +0000, Tom Lane wrote:
> Allow a multi-row INSERT to specify DEFAULTs for a generated column.
> 
> One can say "INSERT INTO tab(generated_col) VALUES (DEFAULT)" and not
> draw an error.  But the equivalent case for a multi-row VALUES list
> always threw an error, even if one properly said DEFAULT in each row.
> Fix that.  While here, improve the test cases for nearby logic about
> OVERRIDING SYSTEM/USER values.
> 
> Dean Rasheed
> 
> Discussion: https://postgr.es/m/9q0sgcr416t.fsf@gmx.us
> 
> Branch
> ------
> master
> 
> Details
> -------
> https://git.postgresql.org/pg/commitdiff/17958972fe3bb03454a4b53756b29d65dc285efa

Shouldn't this be backpatched?
That seems like a clear bug to me; see this report on v11:
https://stackoverflow.com/q/68834080/6464308

Yours,
Laurenz Albe




pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Improve performance of float overflow checks in btree_gist
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Allow a multi-row INSERT to specify DEFAULTs for a generated col