Fix INSERT OVERRIDING USER VALUE behavior
authorPeter Eisentraut <peter@eisentraut.org>
Tue, 31 Mar 2020 06:40:32 +0000 (08:40 +0200)
committerPeter Eisentraut <peter@eisentraut.org>
Tue, 31 Mar 2020 06:50:39 +0000 (08:50 +0200)
commitde3bbfcc962f24c1a20a17b76c604e5973a05817
tree9cf34889eeded6c5b044f294dafb3b37aeb84e70
parent616ae3d2b0566e91b49f301bf08410a9972fed93
Fix INSERT OVERRIDING USER VALUE behavior

The original implementation disallowed using OVERRIDING USER VALUE on
identity columns defined as GENERATED ALWAYS, which is not per
standard.  So allow that now.

Expand documentation and tests around this.

Author: Dean Rasheed <dean.a.rasheed@gmail.com>
Reviewed-by: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Reviewed-by: Vik Fearing <vik@postgresfriends.org>
Discussion: https://www.postgresql.org/message-id/flat/CAEZATCVrh2ufCwmzzM%3Dk_OfuLhTTPBJCdFkimst2kry4oHepuQ%40mail.gmail.com
doc/src/sgml/ref/create_table.sgml
doc/src/sgml/ref/insert.sgml
doc/src/sgml/ref/update.sgml
src/backend/rewrite/rewriteHandler.c
src/test/regress/expected/identity.out
src/test/regress/sql/identity.sql