Horton
Menu

Re: SQL:2011 Application Time Update & Delete

Paul A Jungwirth <pj@illuminatedcomputing.com>

View thread
From: Paul A Jungwirth <pj@illuminatedcomputing.com>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Chao Li <li.evan.chao@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-02-20T17:16:11Z
Lists: pgsql-hackers

Attachments

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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Make ExecForPortionOfLeftovers() obey SRF protocol.

  2. Add isolation tests for UPDATE/DELETE FOR PORTION OF

  3. Add UPDATE/DELETE FOR PORTION OF

  4. Record range constructor functions in pg_range

  5. Add range_minus_multi and multirange_minus_multi functions

  6. doc: Add section for temporal tables

  7. Add assertion check for WAL receiver state during stream-archive transition