| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: First draft of PG 19 release notes |
| Date: | 2026-06-08 14:13:33 |
| Message-ID: | aibODYK-IYODcxoe@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jun 7, 2026 at 11:43:16PM -0400, Bruce Momjian wrote:
> > * In section E.1.3.1.1 Optimizer, I think the item
> > "Allow extended statistics on virtual generated columns"
> > should come before all other items, because it's the only one that
> > requires user action in order for them to take advantage of it. All
> > the other items refer to some optimization that occurs automatically.
>
> While the first item in each section is the most important, I then list
> later items in groups that have similar characteristics, which I think
> simplifies reading. While I could order all items in importance order,
> I think it would be much more confusing to read. Right now the item you
> mention is in a group of items about optimizer statistics.
Actually, if there is no "most important" item in a section, I just
order by placing the largest group of similar items first. Here are the
detais:
https://wiki.postgresql.org/wiki/Creating_Major_Release_Notes
order inside of sections
most important item first in section
if none, then largest group first
group similar items together
order group by item importance
ideally the last item in a group will relate to the first item in the next group
--
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 | Bertrand Drouvot | 2026-06-08 14:21:59 | Re: t/035_standby_logical_decoding.pl might fail on attempt to read wrong timeline |
| Previous Message | Álvaro Rodríguez | 2026-06-08 13:50:40 | Unexpected reindex when altering column types for partitioned tables |