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>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-11-05T15:46:20Z
Lists: pgsql-hackers
On 30.10.25 07:02, Paul A Jungwirth wrote: > On Tue, Oct 28, 2025 at 3:49 AM Peter Eisentraut <peter@eisentraut.org> wrote: >> 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. > > Thanks for taking a look! New patches attached; details below. > > Besides addressing your feedback, I corrected a few other details, > like a discrepancy in the valid-times between the SQL, the diagrams, > and the SELECT output. > >> 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. > > Okay, done. This separation makes it a little awkward to continue the > example from the PKs/FKs section, but I included a link and repeated > the table contents, so I think it is okay. I agree it fits better into > the existing overall structure. I committed the patches 0001 and 0002 (from v59). I massaged it a bit to fit better into the flow of the chapter. For example, there was already a "products" table mentioned earlier in the chapter, and I made the new one more similar to that one, so that it can be seen as an enhancement of what was already discussed. Similarly, I changed the ALTER TABLE commands into CREATE TABLE, because in the chapter, the ALTER TABLE commands are not discussed until after the new section. I also added some <emphasis> to the command examples, similar to what is done elsewhere. There were some extra blank lines at the beginning of the image sources (.txt), which did show up as extra top padding in the SVG output, which didn't seem right. I removed that and regenerated the images. (Which worked well; I'm glad this pipeline still worked.)
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