2026-02-12 release announcement draft

Started by Jonathan S. Katz5 months ago2 messageshackers
Jump to latest
#1Jonathan S. Katz
jkatz@postgresql.org

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

Attachments:

20260212updaterelease.mdtext/plain; charset=UTF-8; name=20260212updaterelease.mdDownload
#2Xueyu Gao
gaoxueyu_hope@163.com
In reply to: Jonathan S. Katz (#1)
Re:2026-02-12 release announcement draft

At 2026-02-10 08:01:56, "Jonathan S. Katz" <jkatz@postgresql.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