Re: 2025-11-13 release announcement draft - Mailing list pgsql-hackers

From Jonathan S. Katz
Subject Re: 2025-11-13 release announcement draft
Date
Msg-id a4f80c7a-d806-4385-bad3-0f52a0c45b04@postgresql.org
Whole thread Raw
In response to Re: 2025-11-13 release announcement draft  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: 2025-11-13 release announcement draft
List 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@gmail.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

pgsql-hackers by date:

Previous
From: Yugo Nagata
Date:
Subject: Re: Suggestion to add --continue-client-on-abort option to pgbench
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] libpq: Wrap out-of-memory error messages with libpq_gettext()