| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | Petr Hybler <petr(dot)hybler(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | PGSQL bug - "Column ??? is an identity column defined as GENERATED ALWAYS.", |
| Date: | 2021-08-18 21:15:37 |
| Message-ID: | CAKFQuwaGiwrCLEy8C7rkjw8PDCVnDRuc63Fjrotv14eQ9whnpg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wednesday, August 18, 2021, Peter Eisentraut <peter.eisentraut@
enterprisedb.com> wrote:
> On 18.08.21 17:06, Petr Hybler wrote:
>
>> |CREATE TABLE sample_table ( id int8 NOT NULL GENERATED ALWAYS AS
>> IDENTITY, name varchar(255) NOT NULL, description text NOT NULL, CONSTRAINT
>> sample_table_pk PRIMARY KEY (id) );|
>>
>> When I try to insert a single value, it works OK:
>>
>> |INSERT INTO sample_table (id, name, description) VALUES (DEFAULT, 'John
>> Doe', 'Test description');|
>>
>> However, when inserting multiple values, it fails:
>>
>> |INSERT INTO sample_table (id, name, description) VALUES (DEFAULT, 'John
>> Doe', 'Test description') , (DEFAULT, 'Jane Eod', 'Not working');|
>>
>
> This has been fixed in PostgreSQL 14.
>
>
The OP is reporting a regression, saying it is fixed in v14 isn’t a useful
response. Is it also fixed in v11.14?
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-08-18 21:54:36 | Re: PGSQL bug - "Column ??? is an identity column defined as GENERATED ALWAYS.", |
| Previous Message | Peter Eisentraut | 2021-08-18 19:27:18 | Re: PGSQL bug - "Column ??? is an identity column defined as GENERATED ALWAYS.", |