Re: SQL:2011 Application Time Update & Delete

Peter Eisentraut <peter@eisentraut.org>

From: Peter Eisentraut <peter@eisentraut.org>
To: Kirill Reshke <reshkekirill@gmail.com>
Cc: Paul A Jungwirth <pj@illuminatedcomputing.com>, Chao Li <li.evan.chao@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-01-22T15:23:01Z
Lists: pgsql-hackers
On 19.01.26 18:43, Kirill Reshke wrote:
> One stupid question from me: should we add
> 
> ````
>   t.typanalyze!='range_typanalyze'::regproc or t.typinput !=
> 'range_in'::regproc or t.typoutput != 'range_out'::regproc  or
> t.typreceive != 'range_recv'::regproc or typsend !=
> 'range_send'::regproc;
> 
> ````

Maybe, but this seems to be outside of this patch.  There are also 
similar considerations for arrays, domains, etc.



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