Re:2026-02-12 release announcement draft

From: "Xueyu Gao" <gaoxueyu_hope(at)163(dot)com>
To: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Jeff Davis" <pgsql(at)j-davis(dot)com>
Subject: Re:2026-02-12 release announcement draft
Date: 2026-02-10 07:38:12
Message-ID: 36f6f380.4a84.19c467c877e.Coremail.gaoxueyu_hope@163.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 2026-02-10 08:01:56, "Jonathan S. Katz" <jkatz(at)postgresql(dot)org> wrote:
>Hi,
>
>Please see the proposed draft of the 2026-02-12 announcement. Please
>review for errors, typos, notable omissions, etc.
>
>I also wanted to ensure I captured the correct set of post-upgrade steps
>for the `ltree` issue. I tried to simplify it as much as possible while
>trying to convey how narrow the scope of having to reindex. However, if
>I. misunderstood, please help me correct.
>
>Thanks,
>

>Jonathan

Hi Jonathan,

The draft is solid and mostly accurate.

I have only one comment:

“in some cases you may need perform a reindex” should be “in some cases you may need to perform a reindex”.
Thanks,

Hope Gao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2026-02-10 07:46:27 Re: Buffer locking is special (hints, checksums, AIO writes)
Previous Message Bertrand Drouvot 2026-02-10 07:30:50 Re: Adding locks statistics