Re: add list of major features to the v19 release notes

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Michael Banck <mbanck(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: add list of major features to the v19 release notes
Date: 2026-08-25 14:30:18
Message-ID: ao2m-rfWTCtHhxCs@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Aug 22, 2026 at 05:50:56PM -0400, Andrew Dunstan wrote:
> On 2026-08-22 Sa 3:56 PM, Jonathan S. Katz wrote:
>> This has been up for awhile, so I don't want to suggest removing items
>> for this list. That said, I'd like to suggest a few
>> listing/wording/ordering tweaks, primarily to tighten up a few of the
>> explanations and align with the style from previous release notes.
>
> I don't know how the ordering was arrived at. I think we should lead with
> blockbuster items. Everyone will have their own opinion, but in my mind the
> blockbuster items are REPACK and pg_plan_advice.

There wasn't a whole lot of science around the ordering. We did
intentionally put the catch-all performance item at the end, but that was
about the extent of conscious thought about it.

Jonathan's proposed changes seem fine to me at a glance. I'll let that
marinate on the lists a bit more before applying.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2026-08-25 14:47:11 Re: Allow aggressive VACUUM to freeze without a cleanup lock
Previous Message Peter Geoghegan 2026-08-25 14:28:13 Re: Allow aggressive VACUUM to freeze without a cleanup lock