Re: 2025-11-13 release announcement draft

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: 2025-11-13 release announcement draft
Date: 2025-11-11 01:57:32
Message-ID: a4f80c7a-d806-4385-bad3-0f52a0c45b04@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/10/25 4:47 PM, Nathan Bossart wrote:
> On Mon, Nov 10, 2025 at 04:40:57PM -0500, Tom Lane wrote:
>> Nathan Bossart <nathandbossart(at)gmail(dot)com> writes:
>>> On Mon, Nov 10, 2025 at 02:01:14PM -0500, Jonathan S. Katz wrote:
>>>> If you previously created a BRIN index using the `numeric_minmax_multi_ops`
>>>> operator class, please see the "Updating" section for additional instructions
>>>> after upgrading your instance.
>>
>>> It looks like these additional instructions are missing.
>>
>> Isn't that text leftover from the last releases?

Yup, you all caught the copy-and-pasto. I had removed it from the
upgrading instructions but missed the beginning, sorry.

For the point that Nathan nit'd, I just removed it because I couldn't
come up with a pithy way to describe it after reading the release note a
bunch of times. Open to suggestions if we want to include, with revised
wording.

Thanks,

Jonathan

Attachment Content-Type Size
20251113updaterelease.md text/x-markdown 4.2 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-11-11 02:03:22 Re: [PATCH] libpq: Wrap out-of-memory error messages with libpq_gettext()
Previous Message Yugo Nagata 2025-11-11 01:50:37 Re: Suggestion to add --continue-client-on-abort option to pgbench