| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>, David Christensen <david+pg(at)pgguru(dot)net> |
| Subject: | Re: First draft of PG 19 release notes |
| Date: | 2026-05-12 20:27:55 |
| Message-ID: | agONS7g4gNxcS5t5@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 12, 2026 at 08:41:28AM -0400, Greg Sabino Mullane wrote:
> I can kind of understand why this did not make the cut:
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=41d69e6d
>
> (Add labels to help make psql's hidden queries more understandable)
>
> ... but I'm in favor (yes, somewhat selfishly to be honest) of listing all
> changes, no matter how small. Is there a written criteria or guidelines for
> these things? I think the bar is already low if we list things like "improved
> tab completion", TBH.
I am not sure how to answer this except to say that I try to list items
that are important for the general reading audience to know. All
changes are already in the git commit log.
If you would like to make the case that listing all changes would be
helpful for the general reading audience, please make that case. If you
would like to make the case that being most helpful for the general
reading audience is not the right goal, please explain.
--
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-05-12 20:31:42 | Re: First draft of PG 19 release notes |
| Previous Message | Bruce Momjian | 2026-05-12 20:15:22 | Re: First draft of PG 19 release notes |