Re: PG 18 release notes draft committed

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Alexander Borisov <lex(dot)borisov(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PG 18 release notes draft committed
Date: 2025-05-04 20:43:16
Message-ID: 29a7dd7b-cb55-4c3c-8eba-faeca222b10b@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 5/3/25 7:48 PM, Alexander Borisov wrote:
> 04.05.2025 02:28, Bruce Momjian wrote:
>
>
>> It doesn't warrant its own item because it is not user-facing work.  The
>> best we can do is add the commit to an existing item and add you as a
>> co-author on an existing item.  You will see several items that are that
>> way already.
>>
>
> Thank you for clarifying!
> Users are not interested in performance gains.
> Then it's not worth considering. Sorry to interrupt.

I do know that users are interested in performance gains - and it is
definitely user facing - and as such I try to include these things in
the release announcement (which I'm currently drafting) as part of
making the release available. Similarly, we do need to use discretion
with how we discuss performance enhancements in the release announcement
to ensure we make directionally accurate claims and look towards broad
impact.

I've noted the claims on upper/lower; we'll see if it makes the cut in
the release announcement.

Thanks,

Jonathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2025-05-05 00:22:53 Re: PG 18 release notes draft committed
Previous Message Alexander Borisov 2025-05-04 20:28:44 Re: PG 18 release notes draft committed