From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Identity columns, DEFAULT keyword and multi-row inserts |
Date: | 2019-12-10 07:41:37 |
Message-ID: | ae6d3563-f3c9-ce42-1f2c-32934e844505@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
assume the following table:
create table test
(
id integer not null generated always as identity,
data integer not null
);
The following insert works fine:
insert into test (id, data)
values (default,1);
However, a multi-row insert like the following:
insert into test (id, data)
values
(default,1),
(default,2);
fails with:
ERROR: cannot insert into column "id"
Detail: Column "id" is an identity column defined as GENERATED ALWAYS.
Hint: Use OVERRIDING SYSTEM VALUE to override.
My question is:
* If DEFAULT is not allowed for identity columns, then why does the single-row insert work?
* If DEFAULT _is_ allowed, then why does the multi-row insert fail?
The above happens with Postgres 10,11 and 12
Regards
Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Dan shmidt | 2019-12-10 07:55:25 | Logical Replication of Multiple Schema Versions |
Previous Message | Rene Romero Benavides | 2019-12-10 05:54:03 | Re: Tuple concurrency issue in large objects |