| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Tighten check for generated column in partition key expression |
| Date: | 2025-11-04 13:48:04 |
| Message-ID: | E1vGHOG-004zqn-1R@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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(dot)universality(at)gmail(dot)com>
Co-authored-by: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Reviewed-by: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Discussion: https://www.postgresql.org/message-id/flat/CACJufxF%3DWDGthXSAQr9thYUsfx_1_t9E6N8tE3B8EqXcVoVfQw%40mail.gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/040cc5f3c782839ed30816671c5b5f36df0d2398
Modified Files
--------------
src/backend/commands/tablecmds.c | 90 ++++++++++++++-----------
src/test/regress/expected/generated_stored.out | 15 +++++
src/test/regress/expected/generated_virtual.out | 15 +++++
src/test/regress/sql/generated_stored.sql | 3 +
src/test/regress/sql/generated_virtual.sql | 3 +
5 files changed, 86 insertions(+), 40 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2025-11-04 14:42:23 | pgsql: Tighten check for generated column in partition key expression |
| Previous Message | Álvaro Herrera | 2025-11-04 12:24:42 | pgsql: BRIN autosummarization may need a snapshot |