Tighten check for generated column in partition key expression
Peter Eisentraut <peter@eisentraut.org>
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
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/commands/tablecmds.c | modified | +48 −38 |
| src/test/regress/expected/generated.out | modified | +15 −0 |
| src/test/regress/sql/generated.sql | modified | +3 −0 |
Discussion
- bug: virtual generated column can be partition key 18 messages · 2025-04-21 → 2025-11-04