BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: pavel(dot)boev(at)invitae(dot)com
Subject: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
Date: 2021-03-04 04:13:59
Message-ID: 16913-3b5198410f67d8c6@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16913
Logged by: Pavel Boev
Email address: pavel(dot)boev(at)invitae(dot)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.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-03-04 07:43:11 BUG #16914: Regression test of the worker_spi fails if USE_MODULE_DB environment variable is set.
Previous Message PG Bug reporting form 2021-03-03 23:39:11 BUG #16912: pg_dump 11 does not respect --quote-all-identifiers within function bodies