Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\))
Subject: Re: First draft of PG 19 release notes
From: Chao Li <li.evan.chao@gmail.com>
In-Reply-To: <aibODYK-IYODcxoe@momjian.us>
Date: Tue, 9 Jun 2026 14:59:17 +0800
Cc: PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <402C0CBE-B5C3-41BD-9D6D-E739B9E1E390@gmail.com>
References: <aiMcYbhya9eqF4Zr@momjian.us> <aiQPgZtALNqj4npv@alvherre.pgsql>
 <aiY6VAG36CPzfq0l@momjian.us> <aibODYK-IYODcxoe@momjian.us>
To: Bruce Momjian <bruce@momjian.us>
Archived-At: 
 <https://www.postgresql.org/message-id/402C0CBE-B5C3-41BD-9D6D-E739B9E1E390%40gmail.com>
Precedence: bulk


> On Jun 8, 2026, at 22:13, Bruce Momjian <bruce@momjian.us> wrote:
>=20
> 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.
>>=20
>> 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.
>=20
> 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:
>=20
> 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
>=20
> --=20
>  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
>  EDB                                      https://enterprisedb.com
>=20
>  Do not let urgent matters crowd out time for investment in the =
future.
>=20
>=20

Hi Bruce,

This feature has been reverted by =
a0354e29c41a9fb7491b3c7c23f079b1923c045a.

```
<!--
Author: Andrew Dunstan <andrew@dunslane.net>
2026-03-12 [a0b6ef29a] Enable fast default for domains with non-volatile =
constr
-->

<listitem>
<para>
Allow the <link linkend=3D"sql-altertable">addition of columns</link> =
based on domains containing constraints to usually avoid a table rewrite =
(Jian He)
<ulink url=3D"&commit_baseurl;a0b6ef29a">&sect;</ulink>
</para>

<para>
Previously this always required a table rewrite.
</para>
</listitem>
```

So this item can be removed from the release note.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/