MIME-Version: 1.0
References: <e856c439-bf96-4244-8dc3-18b2a552e406@eisentraut.org>
 <CA+renyU6rNkiNGreMyQ7pU_F6-5RND5jchHbECH4NoRO7W0Q-Q@mail.gmail.com>
 <27BD5D23-19C9-4FD1-8935-9C788C3C9869@gmail.com>
 <66C1555B-CA54-4ED1-AB4F-0EE97D24A006@gmail.com>
 <91B35E0F-5DC1-4417-A1B9-FAF4A3DCD2BD@gmail.com>
 <CA+renyUBLAynaj0BKhajB6F=sLuitQkjT+_sOt5HBSRn82iQsw@mail.gmail.com>
 <74C1863C-2C2A-423A-BDE7-0228889F1D80@gmail.com>
 <CA+renyUTzwAMar173cbbxJypChp7s=txxgB+LYJQ5oRZ3a5hYQ@mail.gmail.com>
 <CACJufxFHe9iq50RfgyU3T1_CrB+NfdrjdBUp6NFNtb=Dy5Lf-g@mail.gmail.com>
 <CA+renyX4UaO7T=sC2UcpKUwS2yd7zt3XxOm1MgXv5W82ucbk0w@mail.gmail.com>
 <agOOykf2HV26yVfU@nathan>
 <CA+renyWqeWxSUoohRQ4htfSLCcDVsZ=XwVR7F8-e9GXeH_O13w@mail.gmail.com>
In-Reply-To: 
 <CA+renyWqeWxSUoohRQ4htfSLCcDVsZ=XwVR7F8-e9GXeH_O13w@mail.gmail.com>
From: Paul A Jungwirth <pj@illuminatedcomputing.com>
Date: Wed, 13 May 2026 08:42:53 -0700
Message-ID: 
 <CA+renyVYc-0Swt2sR7vd3V-fu+3s0pZKU9McyznRnzSr1=oeZA@mail.gmail.com>
Subject: Re: FOR PORTION OF does not recompute GENERATED STORED columns that
 depend on the range column
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: jian he <jian.universality@gmail.com>, Chao Li <li.evan.chao@gmail.com>,
	Peter Eisentraut <peter@eisentraut.org>,
 SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BrenyVYc-0Swt2sR7vd3V-fu%2B3s0pZKU9McyznRnzSr1%3DoeZA%40mail.gmail.com>
Precedence: bulk

On Tue, May 12, 2026 at 5:05=E2=80=AFPM Paul A Jungwirth
<pj@illuminatedcomputing.com> wrote:
>
> On Tue, May 12, 2026 at 1:34=E2=80=AFPM Nathan Bossart <nathandbossart@gm=
ail.com> wrote:
> >
> > FOR PORTION OF doesn't seem to work well with virtual generated columns=
,
> > either.  The following example seg-faults on my machine:
> >
> >     create table t (a int, b int4range generated always as (int4range(a=
, a + 1)) virtual);
> >     insert into t values (1);
> >     delete from t for portion of b from 1 to 2;
>
> Thanks for catching this!
>
> Here is a patch forbidding both STORED and VIRTUAL columns here. There
> is a follow-up patch (not for v19) to add SQL:2011 PERIODs, which will
> be based on STORED columns, so we will eventually allow those (if they
> belong to a PERIOD), but it seems right to forbid them for now.
>
> I put the check in the analysis phase to match what we have already,
> but based on [1] that is apparently premature. I think I'd like to
> move all those things together in a single commit though.
>
> I did experiment with putting just this check in ExecInitModifyTable.
> But (1) the planner will already reject the UPDATE case with a
> different error message, and (2) it doesn't really improve anything,
> since rangeVar gets looked up during analysis anyway (until we address
> the rest of [1]).
>
> [1] https://www.postgresql.org/message-id/626986.1776785090%40sss.pgh.pa.=
us

I started a new thread for this issue and made a CF entry. Please see:

- https://www.postgresql.org/message-id/CA%2BrenyVRPyP5TNgEBe%3DhRT1ZR3%3Dz=
WCZLXkAwp5xbWeS_TaMxOA%40mail.gmail.com
- https://commitfest.postgresql.org/patch/6764/

Yours,

--=20
Paul              ~{:-)
pj@illuminatedcomputing.com