pgsql: Forbid generated columns in FOR PORTION OF - Mailing list pgsql-committers

From Peter Eisentraut
Subject pgsql: Forbid generated columns in FOR PORTION OF
Date
Msg-id E1wgdxr-001You-1Q@gemulon.postgresql.org
Whole thread
List 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@illuminatedcomputing.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(-)


pgsql-committers by date:

Previous
From: Richard Guo
Date:
Subject: pgsql: Fix qual pushdown past grouping with mismatched equivalence
Next
From: Peter Eisentraut
Date:
Subject: pgsql: Remove apparent support for SECURITY LABEL ON PROPERTY GRAPH