Re: SQL:2011 Application Time Update & Delete
Paul A Jungwirth <pj@illuminatedcomputing.com>
From: Paul A Jungwirth <pj@illuminatedcomputing.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Peter Eisentraut <peter@eisentraut.org>
Date: 2025-08-29T13:03:44Z
Lists: pgsql-hackers
Attachments
- v53-0001-Add-docs-chapter-for-temporal-tables.patch (application/octet-stream) patch v53-0001
- v53-0002-Document-temporal-foreign-keys.patch (application/octet-stream) patch v53-0002
- v53-0004-Document-temporal-update-delete.patch (application/octet-stream) patch v53-0004
- v53-0003-Document-temporal-PERIODs.patch (application/octet-stream) patch v53-0003
- v53-0005-Add-range_minus_multi-and-multirange_minus_multi.patch (application/octet-stream) patch v53-0005
- v53-0006-Add-UPDATE-DELETE-FOR-PORTION-OF.patch (application/octet-stream) patch v53-0006
- v53-0008-Look-up-more-temporal-foreign-key-helper-procs.patch (application/octet-stream) patch v53-0008
- v53-0007-Add-tg_temporal-to-TriggerData.patch (application/octet-stream) patch v53-0007
- v53-0010-Expose-FOR-PORTION-OF-to-plpgsql-triggers.patch (application/octet-stream) patch v53-0010
- v53-0009-Add-CASCADE-SET-NULL-SET-DEFAULT-for-temporal-fo.patch (application/octet-stream) patch v53-0009
On Sun, Jun 22, 2025 at 6:19 PM Paul A Jungwirth
<pj@illuminatedcomputing.com> wrote:
> Here are updated patches for UPDATE/DELETE FOR PORTION OF and related
> functionality. I left out the usual PERIODs patch because I'm still
> updating it to work with the latest master.
Here is a new set of patches, rebased to 325fc0ab14. No material changes.
I'm still working on the PERIOD DDL, but that doesn't have to go in at
the same time. The tricky part is ALTER TABLE ADD PERIOD, where I need
to wait until the add-columns pass to see the start/end columns'
type/etc, but then in that same pass I need to add a generated range
column. If I add the column in a later pass, I get a failure, e.g.
"cannot ALTER TABLE "pt" because it is being used by active queries in
this session". This only appeared with recent(ish) NOT NULL work. I
think the solution is to avoid holding a relcache entry longer than
needed, but I haven't had a chance to locate the issue yet.
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 →
-
Make ExecForPortionOfLeftovers() obey SRF protocol.
- 207cb2abcba0 19 (unreleased) landed
-
Add isolation tests for UPDATE/DELETE FOR PORTION OF
- b6ccd30d8ff6 19 (unreleased) landed
-
Add UPDATE/DELETE FOR PORTION OF
- 8e72d914c528 19 (unreleased) landed
-
Record range constructor functions in pg_range
- c257ba839718 19 (unreleased) landed
-
Add range_minus_multi and multirange_minus_multi functions
- 5eed8ce50ce9 19 (unreleased) landed
-
doc: Add section for temporal tables
- e4d8a2af07f5 19 (unreleased) landed
-
Add assertion check for WAL receiver state during stream-archive transition
- 65f4976189b6 19 (unreleased) cited