Re: PG 18 relnotes and RC1
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: Peter Eisentraut <peter@eisentraut.org>,
Nathan Bossart <nathandbossart@gmail.com>, Bruce Momjian <bruce@momjian.us>, PostgreSQL-development <pgsql-hackers@lists.postgresql.org>,
corey.huinker@gmail.com
Date: 2025-09-18T17:38:44Z
Lists: pgsql-hackers
On Thu, Sep 18, 2025 at 12:59 PM Jonathan S. Katz <jkatz@postgresql.org> wrote: > > I like Nathan's version better. I suggest we go with that one. > > Why? This seems arbitrary without more details. > > I’ve spent the past several weeks staring at the release notes, talking to users, and putting together a presentation on it that was delivered last night, also culminating in the press release. I put a lot of effort into researching what to highlight up top, which is augmented in the release details itself. Additionally I started from what Nathan had and tweaked a few items. That seems completely backwards to me. We should go with the version that was submitted weeks ago and upon which people have had the opportunity to comment unless you can justify each change that you now want to make at the last minute. Why for example should we drop mentioning the ability to return OLD.* and NEW.* in favor of mentioned UUIDv7? I'd argue that the former is more important than the latter, and I don't see how you can argue otherwise except by appealing to the research you've done over the last several weeks. But none of us have access to that or got a vote in it. These things ought to be decided by consensus. If you want your research to feed into the building of that consensus, you need to do it and present it earlier. For example, if you want to present survey results, I think that's a great way to help decide these kinds of things, but then other people should have the right to present their own survey results and so on in that conversation too. -- Robert Haas EDB: http://www.enterprisedb.com
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add list of major features to the v18 release notes.
- b585f25284d2 18.0 landed
-
add_commit_links.pl: error out if missing major version number
- 0c6d572c1173 19 (unreleased) landed
-
doc PG 18 relnotes: Add migration note about tsearch
- d1073c3b4cc8 18.0 cited
-
Remove ts_locale.c's lowerstr()
- fb1a18810f07 18.0 cited