Re: PG 18 relnotes and RC1

Peter Eisentraut <peter@eisentraut.org>

From: Peter Eisentraut <peter@eisentraut.org>
To: Tom Lane <tgl@sss.pgh.pa.us>, Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Date: 2025-08-31T11:34:26Z
Lists: pgsql-hackers
On 30.08.25 18:52, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
>> Second, the release note item added by this commit:
>> 	commit d1073c3b4cc
>> 	Author: Peter Eisentraut <peter@eisentraut.org>
>> 	Date:   Fri Aug 29 10:18:10 2025 +0200
> 
>> Unfortunately src/tools/add_commit_links.pl can't process the <ulink>
>> and throws an error because the previous line does not end with a
>> parenthesis.  If I add "()" after the last line in the text block, it
>> works fine, but obviously this is not acceptable.
> 
> I suppose that the expectation is that every release note item
> will be credited to someone.  Why does this item lack a credit?

Maybe I'm understanding this differently, but the "Migration" section 
ought to be advice about the migration, which is not a place to 
communicate credit.  In the case I added, the item is the result of some 
changes that are already listed and credited elsewhere in the "Changes" 
section.




Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Add list of major features to the v18 release notes.

  2. add_commit_links.pl: error out if missing major version number

  3. doc PG 18 relnotes: Add migration note about tsearch

  4. Remove ts_locale.c's lowerstr()