Re: SQL:2011 Application Time Update & Delete
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Paul A Jungwirth <pj@illuminatedcomputing.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-10-28T10:49:35Z
Lists: pgsql-hackers
On 24.10.25 19:08, Paul A Jungwirth wrote: > The first 3 doc patches all apply to features that we released in v18, > so it would be nice to get those reviewed/merged soon if possible. I have looked through the documentation patches 0001 through 0003. I suggest making the Temporal Tables chapter a section instead. It doesn't feel big enough to be a top-level topic. I think it would fit well into the Data Definition chapter, perhaps after the "System Columns" section (section 5.6). And then the temporal update and delete material would go into the Data Manipulation chapter. The syntax examples for temporal primary keys would be better if they used complete CREATE TABLE examples instead of ALTER TABLE on some table that is presumed to exist. (Or you could link to where in the documentation the table is created.) The PostgreSQL documentation is not really a place to describe features that don't exist. So while it's okay to mention system time in the glossary because it contrasts with application time, it doesn't seem appropriate to elaborate further on this in the main body of the documentation, unless we actually implement it. Similarly with periods, we can document them when we have them, but before that it's just a distraction. The pictures are nice. Again, it would be helpful if you showed the full CREATE TABLE statement beforehand, so that it is easier to picture when kind of table structure is being reflected. Initially, I read $5, $8, etc. as parameter numbers, not as prices. Perhaps possible confusion could be avoided if you notionally make the price column of type numeric and show the prices like 5.00, 8.00, etc. I also looked over the patch "Add UPDATE/DELETE FOR PORTION OF" a bit. I think it has a good structure now. I'll do a more detailed review soon.
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