| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: First draft of PG 19 release notes |
| Date: | 2026-06-09 06:59:17 |
| Message-ID: | 402C0CBE-B5C3-41BD-9D6D-E739B9E1E390@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Jun 8, 2026, at 22:13, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> 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.
>
>
Hi Bruce,
This feature has been reverted by a0354e29c41a9fb7491b3c7c23f079b1923c045a.
```
<!--
Author: Andrew Dunstan <andrew(at)dunslane(dot)net>
2026-03-12 [a0b6ef29a] Enable fast default for domains with non-volatile constr
-->
<listitem>
<para>
Allow the <link linkend="sql-altertable">addition of columns</link> based on domains containing constraints to usually avoid a table rewrite (Jian He)
<ulink url="&commit_baseurl;a0b6ef29a">§</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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tingchuan Sun | 2026-06-09 07:01:21 | Re: Fix unqualified catalog references in psql describe queries |
| Previous Message | Bertrand Drouvot | 2026-06-09 06:47:06 | Re: Avoid orphaned objects dependencies, take 3 |