Re: SQL:2011 Application Time Update & Delete

Paul A Jungwirth <pj@illuminatedcomputing.com>

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-13T20:00:52Z
Lists: pgsql-hackers

Attachments

On Wed, Feb 11, 2026 at 1:25 PM Paul A Jungwirth
<pj@illuminatedcomputing.com> wrote:
>
> On Thu, Jan 22, 2026 at 7:21 AM Peter Eisentraut <peter@eisentraut.org> wrote:
> >
> > I have committed the pg_range patch.
>
> Thanks! Here are v65 patches for UPDATE/DELETE FOR PORTION OF. I kept
> the get_range_constructor2 helper function as a separate patch, but it
> probably doesn't really need to be a separate commit. Maybe it could
> even be inlined into its caller.

Here is another round to fix a few rebase conflicts.

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