public inbox for [email protected]  
help / color / mirror / Atom feed
From: Bruce Momjian <[email protected]>
To: Álvaro Herrera <[email protected]>
Cc: Yugo Nagata <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: First draft of PG 19 release notes
Date: Mon, 8 Jun 2026 10:13:33 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

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  <[email protected]>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.






view thread (27+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: First draft of PG 19 release notes
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox