summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-03-12 11:08:42 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2021-03-12 11:08:42 -0500
commite5794cd593940e48710693c0cdd97c6d7b91f500 (patch)
treed0c7cf1465b370ce7212d2d3ec6d3caefb8dd9c6 /doc/src
parentd2be6cdc55ad0eb0fa019a453491e1410c5315e8 (diff)
Forbid marking an identity column as nullable.
GENERATED ALWAYS AS IDENTITY implies NOT NULL, but the code failed to complain if you overrode that with "GENERATED ALWAYS AS IDENTITY NULL". One might think the old behavior was a feature, but it was inconsistent because the outcome varied depending on the order of the clauses, so it seems to have been just an oversight. Per bug #16913 from Pavel Boev. Back-patch to v10 where identity columns were introduced. Vik Fearing (minor tweaks by me) Discussion: https://postgr.es/m/16913-3b5198410f67d8c6@postgresql.org
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/ref/create_table.sgml1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml
index 7d00d22c646..f12e76c2efc 100644
--- a/doc/src/sgml/ref/create_table.sgml
+++ b/doc/src/sgml/ref/create_table.sgml
@@ -689,6 +689,7 @@ FROM ( { <replaceable class="PARAMETER">numeric_literal</replaceable> | <replace
column</firstterm>. It will have an implicit sequence attached to it
and the column in new rows will automatically have values from the
sequence assigned to it.
+ Such a column is implicitly <literal>NOT NULL</literal>.
</para>
<para>