pgsql: Forbid generated columns in FOR PORTION OF

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Forbid generated columns in FOR PORTION OF
Date: 2026-07-06 07:42:03
Message-ID: E1wgdxr-001You-1Q@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Forbid generated columns in FOR PORTION OF

With virtual generated columns there is no column to assign to, and we
shouldn't assign directly to stored generated columns either. (Once
we have PERIODs, we will allow a stored generated column here, but we
will assign to its start/end inputs.)

We can't do this in parse analysis, because views haven't yet been
rewritten, so they mask generated columns.

Author: Paul A. Jungwirth <pj(at)illuminatedcomputing(dot)com>
Discussion: https://www.postgresql.org/message-id/agOOykf2HV26yVfU%40nathan

Branch
------
REL_19_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/c8d49ffb007b2f5aff61cff2ff68786f2d53ac5d

Modified Files
--------------
doc/src/sgml/ddl.sgml | 4 +-
src/backend/optimizer/plan/planner.c | 26 ++++++++++
src/test/regress/expected/for_portion_of.out | 73 ++++++++++++++++++++++++++++
src/test/regress/sql/for_portion_of.sql | 57 ++++++++++++++++++++++
4 files changed, 159 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2026-07-06 10:22:19 pgsql: Remove apparent support for SECURITY LABEL ON PROPERTY GRAPH
Previous Message Richard Guo 2026-07-06 07:16:27 pgsql: Fix qual pushdown past grouping with mismatched equivalence