]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Tighten check for generated column in partition key expression
authorPeter Eisentraut <peter@eisentraut.org>
Tue, 4 Nov 2025 13:31:57 +0000 (14:31 +0100)
committerPeter Eisentraut <peter@eisentraut.org>
Tue, 4 Nov 2025 13:46:58 +0000 (14:46 +0100)
commit040cc5f3c782839ed30816671c5b5f36df0d2398
tree03e4d70c068f88e64bab8929581c29ada8a0bd9c
parenta95e3d84c0e0ffd1e27c185dd69d053e43f2f8b5
Tighten check for generated column in partition key expression

A generated column may end up being part of the partition key
expression, if it's specified as an expression e.g. "(<generated
column name>)" or if the partition key expression contains a whole-row
reference, even though we do not allow a generated column to be part
of partition key expression.  Fix this hole.

Co-authored-by: jian he <jian.universality@gmail.com>
Co-authored-by: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Reviewed-by: Fujii Masao <masao.fujii@oss.nttdata.com>
Discussion: https://www.postgresql.org/message-id/flat/CACJufxF%3DWDGthXSAQr9thYUsfx_1_t9E6N8tE3B8EqXcVoVfQw%40mail.gmail.com
src/backend/commands/tablecmds.c
src/test/regress/expected/generated_stored.out
src/test/regress/expected/generated_virtual.out
src/test/regress/sql/generated_stored.sql
src/test/regress/sql/generated_virtual.sql