Re: SQL:2011 Application Time Update & Delete - Mailing list pgsql-hackers

From Paul A Jungwirth
Subject Re: SQL:2011 Application Time Update & Delete
Date
Msg-id CA+renyV4tWU2d=n9_v=XNPHbZfNqqLokzd-Xt78M-zLd+46ubA@mail.gmail.com
Whole thread
In response to Re: SQL:2011 Application Time Update & Delete  (Paul A Jungwirth <pj@illuminatedcomputing.com>)
Responses Re: SQL:2011 Application Time Update & Delete
Re: SQL:2011 Application Time Update & Delete
List pgsql-hackers
On Fri, Feb 13, 2026 at 12:00 PM Paul A Jungwirth
<pj@illuminatedcomputing.com> wrote:
>
> Here is another round to fix a few rebase conflicts.

I realized we didn't have any tests for v18's new feature to say
`UPDATE ... RETURNING OLD.foo, NEW.foo`. These patches add a small
test for `RETURNING OLD.valid_at, NEW.valid_at` when you say `UPDATE
FOR PORTION OF valid_at`. This seems worth testing since that column
gets set in an automatic way, not via the normal SET syntax. No fixes
were needed.

I also corrected the commit message, which still referred to the
without_overlaps function that we renamed to
{range,multirange}_minus_multi.

As far as I know nothing else here is waiting on me, but please
correct me if I've overlooked something.

Rebased to 18bcdb75d1.

Yours,

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

Attachment

pgsql-hackers by date:

Previous
From: Alexandre Felipe
Date:
Subject: Re: Regression failures after changing PostgreSQL blocksize
Next
From: Bertrand Drouvot
Date:
Subject: Re: Adding locks statistics