Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wWajT-002ito-2o for pgsql-hackers@arkaria.postgresql.org; Mon, 08 Jun 2026 14:13:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wWajS-002eys-1y for pgsql-hackers@arkaria.postgresql.org; Mon, 08 Jun 2026 14:13:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wWajS-002eyk-0s for pgsql-hackers@lists.postgresql.org; Mon, 08 Jun 2026 14:13:38 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wWajP-00000001ywL-40fM for pgsql-hackers@lists.postgresql.org; Mon, 08 Jun 2026 14:13:37 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2026010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=l0gpt8oiMf4wRR5JXVDQaNpgeOyu8HQbvBZ4X6JlVWo=; b=MFOBQ Xp/6jM73rYolX921BIAISfzMMJt3we7oqCSds3oAZB084c2IMEIMCl9jjpdV7ZFqqiYiYT/bBdv8D wviCsdyynhwWuzkq6OWqhdDurQK/aS0jMBIgvI9xFTXRg7cTiLZnPc9p3NGKnBF6DC2U3T9dudLjP luhtUeCjQqO3kK5ryqEiXzOcwq9gEGKyh3YoIMO8sX+dTgXOk3fzuwgu/FVX5F4RY4+prAz8i70bA IKfAcpT+YXMygwXrysvZyup4IvAXjswB/75jcmnNXi05L2279ZFVRusgywlo6usUlWivgl1/2Poo5 7hrLcm8dDOFf/AqInVb5OgSaUjUng==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1wWajN-0000000G1pO-1gBA; Mon, 08 Jun 2026 10:13:33 -0400 Date: Mon, 8 Jun 2026 10:13:33 -0400 From: Bruce Momjian To: =?utf-8?Q?=C3=81lvaro?= Herrera Cc: Yugo Nagata , PostgreSQL-development Subject: Re: First draft of PG 19 release notes Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.