MIME-Version: 1.0
References: <ec498c3d-5f2b-48ec-b989-5561c8aa2024@illuminatedcomputing.com>
 <85ac7f0e-d95f-4377-ade0-8941fd328012@eisentraut.org>
 <CA+renyUazgR-hB_6RY60n23L0y-n_h9G1AappZmPENO0k5pL1g@mail.gmail.com>
 <7d63ddfa-c735-4dfe-8c7a-4f1e2a621058@eisentraut.org>
 <CA+renyVXg5pV84wQnGQuK8-=qoKw3BiBgQzesxM_LkcxxWmYjA@mail.gmail.com>
 <e59d218a-ae49-490f-ae6f-86c12f35d3c3@eisentraut.org>
 <CA+renyWKOj5=rMmQmJcbybu-Vdomxdp=eJ93kp76AgmQKYdfiQ@mail.gmail.com>
 <4606deaa-7d65-4f22-8a78-356c3180be9d@eisentraut.org>
 <CA+renyUhuXB2nTVCMREXew9E4DZOnFxQNjME5bcw91+k72Bosg@mail.gmail.com>
 <CA+renyWUCSyTMn3s03kviEN-oaVrJP-QkDQCLNfaY=MHV5QEiQ@mail.gmail.com>
 <CA+renyV4tWU2d=n9_v=XNPHbZfNqqLokzd-Xt78M-zLd+46ubA@mail.gmail.com>
 <53f1c094-3c29-4ef6-a9bd-dc2e7894ceb0@eisentraut.org>
 <CA+renyUSgqXpjj+vV7w+wirPB49VQFrmPjVT_s04JmZSOPNNsQ@mail.gmail.com>
 <b2ecbf9f-797f-433d-953f-3c848cde5a1c@eisentraut.org>
 <CA+renyX-eV+2hFUaZg3BSREqLE7dh+LoWm7ZqhFAiGsirjjtRQ@mail.gmail.com>
 <e2fc32a4-319b-4176-8bd8-1d974e31376f@eisentraut.org>
 <CAHg+QDckLFqthQyox2NDetYRs9sRrjmAiSA-gYRowyg8w_4vgw@mail.gmail.com>
In-Reply-To: 
 <CAHg+QDckLFqthQyox2NDetYRs9sRrjmAiSA-gYRowyg8w_4vgw@mail.gmail.com>
From: SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
Date: Thu, 9 Apr 2026 12:35:13 -0700
Message-ID: 
 <CAHg+QDd74fnd4obCRMqVS0AVWf=cSFH=Cv7trTJWgm+_bhTK6w@mail.gmail.com>
Subject: Re: SQL:2011 Application Time Update & Delete
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Paul A Jungwirth <pj@illuminatedcomputing.com>,
 Chao Li <li.evan.chao@gmail.com>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000002d2d74064f0c1e8c"
Archived-At: 
 <https://www.postgresql.org/message-id/CAHg%2BQDd74fnd4obCRMqVS0AVWf%3DcSFH%3DCv7trTJWgm%2B_bhTK6w%40mail.gmail.com>
Precedence: bulk

--0000000000002d2d74064f0c1e8c
Content-Type: text/plain; charset="UTF-8"

Hi Paul, Peter,

I found a Server crash when using UPDATE ... FOR PORTION OF or DELETE ...
FOR PORTION OF on a view that has INSTEAD OF triggers.

Repro:

CREATE TABLE t (id INT, valid_at daterange, val INT);
INSERT INTO t VALUES (1, '[2026-01-01,2026-12-31)', 100);
CREATE VIEW v AS SELECT * FROM t;

CREATE FUNCTION v_trig() RETURNS trigger LANGUAGE plpgsql AS $$
BEGIN
    UPDATE t SET val = NEW.val WHERE id = OLD.id;
    RETURN NEW;
END;
$$;
CREATE TRIGGER trg INSTEAD OF UPDATE ON v
    FOR EACH ROW EXECUTE FUNCTION v_trig();

-- This crashes the server:
UPDATE v FOR PORTION OF valid_at FROM '2026-04-01' TO '2026-08-01'
    SET val = 999 WHERE id = 1;

I am thinking we should just reject this case. Attached a draft patch to
fix the issue.

Thanks,
Satya

--0000000000002d2d74064f0c1e8c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>Hi Paul, Peter,</div><div><br></div>=
<div>I found a Server crash when using UPDATE ... FOR PORTION OF or DELETE =
... FOR PORTION OF on a view that has INSTEAD OF triggers.<br><br>Repro:</d=
iv><div><br>CREATE TABLE t (id INT, valid_at daterange, val INT);<br>INSERT=
 INTO t VALUES (1, &#39;[2026-01-01,2026-12-31)&#39;, 100);<br>CREATE VIEW =
v AS SELECT * FROM t;<br><br>CREATE FUNCTION v_trig() RETURNS trigger LANGU=
AGE plpgsql AS $$<br>BEGIN<br>=C2=A0 =C2=A0 UPDATE t SET val =3D NEW.val WH=
ERE id =3D OLD.id;<br>=C2=A0 =C2=A0 RETURN NEW;<br>END;<br>$$;<br>CREATE TR=
IGGER trg INSTEAD OF UPDATE ON v<br>=C2=A0 =C2=A0 FOR EACH ROW EXECUTE FUNC=
TION v_trig();<br><br>-- This crashes the server:<br>UPDATE v FOR PORTION O=
F valid_at FROM &#39;2026-04-01&#39; TO &#39;2026-08-01&#39;<br>=C2=A0 =C2=
=A0 SET val =3D 999 WHERE id =3D 1;<br><br>I am thinking we should just rej=
ect this case. Attached a draft patch to fix the issue.=C2=A0</div></div><d=
iv dir=3D"ltr"><br></div>Thanks,<div>Satya</div></div>

--0000000000002d2d74064f0c1e8c--