agora inbox for pgsql-committers@postgresql.orghelp / color / mirror / Atom feed
pgsql: Forbid generated columns in FOR PORTION OF 2+ messages / 1 participants [nested] [flat]
* pgsql: Forbid generated columns in FOR PORTION OF @ 2026-07-06 07:42 Peter Eisentraut <peter@eisentraut.org> 0 siblings, 0 replies; 2+ messages in thread From: Peter Eisentraut @ 2026-07-06 07:42 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 ------ master Details ------- https://git.postgresql.org/pg/commitdiff/e994f956e4864f424320f5243b9af11e173ad398 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(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: Forbid generated columns in FOR PORTION OF @ 2026-07-06 07:42 Peter Eisentraut <peter@eisentraut.org> 0 siblings, 0 replies; 2+ messages in thread From: Peter Eisentraut @ 2026-07-06 07:42 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2026-07-06 07:42 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-07-06 07:42 pgsql: Forbid generated columns in FOR PORTION OF Peter Eisentraut <peter@eisentraut.org> 2026-07-06 07:42 pgsql: Forbid generated columns in FOR PORTION OF Peter Eisentraut <peter@eisentraut.org>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox