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

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: 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 15:52:32
Message-ID: ce01d8e1-b653-4c04-91d7-54163f706795@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/25/26 10:30 AM, Nathan Bossart wrote:
> 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.

"Blockbuster" means different things to different people - when I
propose ordering, I'm typically looking for an optimization around how
many users does the change impact and how resounding that impact is.

That said, in the proposed patch I did shuffle the order around that
algorithm - if needed I'm happy to detail the thinking more, but I like
to be careful around this given people have put a lot of work and effort
into all the patches and did work specifically because they want to make
things better/easier for users.

> 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.
Thanks; happy to make additional tweaks if need be.

Thanks,

Jonathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2026-08-25 15:57:01 Re: Disallow outer-level and WHERE-clause aggregates in GRAPH_TABLE
Previous Message Jacob Champion 2026-08-25 15:44:21 Re: Coverage (lcov) failing with inconsistent error in versions 2.x