diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2025-11-04 14:31:57 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2025-11-04 14:46:58 +0100 |
| commit | 040cc5f3c782839ed30816671c5b5f36df0d2398 (patch) | |
| tree | 03e4d70c068f88e64bab8929581c29ada8a0bd9c /src/include/parser/parser.h | |
| parent | a95e3d84c0e0ffd1e27c185dd69d053e43f2f8b5 (diff) | |
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
Diffstat (limited to 'src/include/parser/parser.h')
0 files changed, 0 insertions, 0 deletions