mirror of
https://github.com/postgres/postgres.git
synced 2025-07-07 00:36:50 +03:00
Catch syntax error in generated column definition
The syntax GENERATED BY DEFAULT AS (expr) is not allowed but we have to accept it in the grammar to avoid shift/reduce conflicts because of the similar syntax for identity columns. The existing code just ignored this, incorrectly. Add an explicit error check and a bespoke error message. Reported-by: Justin Pryzby <pryzby@telsasoft.com>
This commit is contained in:
@ -3505,6 +3505,19 @@ ColConstraintElem:
|
||||
n->raw_expr = $5;
|
||||
n->cooked_expr = NULL;
|
||||
n->location = @1;
|
||||
|
||||
/*
|
||||
* Can't do this in the grammar because of shift/reduce
|
||||
* conflicts. (IDENTITY allows both ALWAYS and BY
|
||||
* DEFAULT, but generated columns only allow ALWAYS.) We
|
||||
* can also give a more useful error message and location.
|
||||
*/
|
||||
if ($2 != ATTRIBUTE_IDENTITY_ALWAYS)
|
||||
ereport(ERROR,
|
||||
(errcode(ERRCODE_SYNTAX_ERROR),
|
||||
errmsg("for a generated column, GENERATED ALWAYS must be specified"),
|
||||
parser_errposition(@2)));
|
||||
|
||||
$$ = (Node *)n;
|
||||
}
|
||||
| REFERENCES qualified_name opt_column_list key_match key_actions
|
||||
|
Reference in New Issue
Block a user