From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: pavel.boev@invitae.com
Subject: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
Date: Thu, 04 Mar 2021 04:13:59 +0000
Message-ID: <16913-3b5198410f67d8c6@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 16913
Logged by: Pavel Boev
Email address: pavel.boev@invitae.com
PostgreSQL version: 13.2
Operating system: Debian 8.3.0-6
Description:
I noticed that nullability of columns having GENERATED AS IDENTITY option is
affected by the order of NULL option, so the next query will create a
"my_table" table having non-nullable column "generated":
create table my_table (
generated integer null generated by default as identity,
data text not null
);
Whereas the following query will create a "my_table" table having nullable
column "generated":
create table my_table (
generated integer generated by default as identity null,
data text not null
);
I noticed the issue appeared in postgres 13.2, however folks say that they
bug affects versions 10, 11 and 12 as well.
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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, pavel.boev@invitae.com
Subject: Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
In-Reply-To: <16913-3b5198410f67d8c6@postgresql.org>
* 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