Thread: First-draft back-branch release notes are up
Much less exciting than the v18 release notes, but we still gotta do 'em. See https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=176877f461a8b55e921f597fb217f6ab89ee019f As usual, please send corrections by Sunday. regards, tom lane
On Fri, May 2, 2025 at 12:39:15PM -0400, Tom Lane wrote: > Much less exciting than the v18 release notes, but we > still gotta do 'em. See > > https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=176877f461a8b55e921f597fb217f6ab89ee019f > > As usual, please send corrections by Sunday. They look good to me, as does my entry: <!-- Author: Bruce Momjian <bruce@momjian.us> Branch: master [46b4ba533] 2025-04-07 21:33:42 -0400 Branch: REL_17_STABLE [b8b1e87b7] 2025-04-07 21:33:41 -0400 --> <para> Avoid incorrect optimizations based on <literal>IS [NOT] NULL</literal> tests that are applied to composite values (Bruce Momjian) <ulink url="&commit_baseurl;b8b1e87b7">§</ulink> </para> </listitem> My commit message erroneously said "domains" instead of "composite values". -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.
On Sat, May 3, 2025 at 12:39 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Much less exciting than the v18 release notes, but we > still gotta do 'em. See > > https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=176877f461a8b55e921f597fb217f6ab89ee019f > > As usual, please send corrections by Sunday. > +<!-- +Author: Tom Lane <tgl@sss.pgh.pa.us> +Branch: master [95f650674] 2025-03-03 12:43:44 -0500 +Branch: REL_17_STABLE [d6dd2a02b] 2025-03-03 12:43:29 -0500 +Branch: REL_16_STABLE [edc3bccd0] 2025-03-03 12:43:29 -0500 +Branch: REL_15_STABLE [1d180931c] 2025-03-03 12:43:29 -0500 +Branch: REL_14_STABLE [c75c830e2] 2025-03-03 12:43:29 -0500 +Branch: REL_13_STABLE [aac07b562] 2025-03-03 12:43:29 -0500 +Branch: master [bd178960c] 2025-04-02 11:13:01 -0400 +Branch: REL_17_STABLE [0941aadcd] 2025-04-02 11:13:01 -0400 +Branch: REL_16_STABLE [053222a97] 2025-04-02 11:13:01 -0400 +Branch: REL_15_STABLE [2d6cfb0cd] 2025-04-02 11:13:01 -0400 +Branch: REL_14_STABLE [d31d39cfe] 2025-04-02 11:13:01 -0400 +Branch: REL_13_STABLE [dd34cbfce] 2025-04-02 11:13:01 -0400 +--> + <para> + Fix <literal>ALTER TABLE ADD COLUMN</literal> to correctly handle + the case of a domain type that has a default (Tom Lane, Tender Wang) + </para> + + <para> + If a domain type has a default, adding a column of that type (without + any explicit <literal>DEFAULT</literal> + clause) failed to install the domain's default + value in existing rows, instead leaving the new column null. + </para> + </listitem> + + <listitem> we have two commits, https://git.postgresql.org/cgit/postgresql.git/commit/?id=d6dd2a02bae0d67ff6fbd73068dc36d0b82fc14b and https://git.postgresql.org/cgit/postgresql.git/commit/?id=bd178960c69bae972c274af8102da9018df8196a we should include both commit's authors... BTW, I found that for minor releases, bug reporter is not included....
jian he <jian.universality@gmail.com> writes: > we have two commits, > https://git.postgresql.org/cgit/postgresql.git/commit/?id=d6dd2a02bae0d67ff6fbd73068dc36d0b82fc14b > and > https://git.postgresql.org/cgit/postgresql.git/commit/?id=bd178960c69bae972c274af8102da9018df8196a > we should include both commit's authors... Argh --- yes, I missed you in crediting that one. My apologies, will fix tomorrow. > BTW, I found that for minor releases, bug reporter is not included.... No, we generally haven't done that in release notes, only in the commit log. I think the only cases where we credit reporters in the release notes are CVE-worthy security bugs. regards, tom lane