| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Allow a multi-row INSERT to specify DEFAULTs for a generated col |
| Date: | 2021-08-19 03:14:11 |
| Message-ID: | 6906fe3025b8a8fc7a3c1f120b93726db53c7ed3.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-08-19 03:17:31 | Re: pgsql: Allow a multi-row INSERT to specify DEFAULTs for a generated col |
| Previous Message | Michael Paquier | 2021-08-19 01:46:03 | pgsql: Improve performance of float overflow checks in btree_gist |