| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, David Geier <geidav(dot)pg(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: First draft of PG 19 release notes |
| Date: | 2026-04-21 20:41:36 |
| Message-ID: | aefhAMDPsOCNa_DY@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 21, 2026 at 11:52:37AM -0400, Andres Freund wrote:
> FWIW, I think it's totally fine if you say that you don't want to do the work
> to formulate performance improvement release note entries. It's a lot of work
> to curate the release notes, it makes sense to split the work up.
>
> It's just that the answer to proposing listing certain performance
> improvements shouldn't be that we don't include them as a matter of policy.
I am fine with listing anything, as long as it is effective and useful
to the reader. I explained in my recent email why I considered that to
be very hard for performance items, but with help I think it can be
achieved. New optimizer items are a good example --- we reference plan
types. I need help in how other items can have similar effectiveness.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2026-04-21 21:17:13 | Re: First draft of PG 19 release notes |
| Previous Message | Bruce Momjian | 2026-04-21 20:28:09 | Re: First draft of PG 19 release notes |