Re: PG 18 relnotes and RC1

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter@eisentraut.org>, PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Date: 2025-08-31T18:11:29Z
Lists: pgsql-hackers
On Sun, Aug 31, 2025 at 10:34:43AM -0400, Tom Lane wrote:
> Peter Eisentraut <peter@eisentraut.org> writes:
> > On 30.08.25 18:52, Tom Lane wrote:
> >> 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.
> 
> One answer could be to remove the commit-details comment block from
> that item, thereby making the added URL go away too.  However, that
> will look a bit odd when the neighboring items all have credits and
> URLs.

Yes, and that would make it hard to find the commit used for the change,
which can be helpful for users.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.



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()