Обсуждение: 2025-11-13 release announcement draft

Hi,

Attached is a draft of the 2025-11-13 release announcement. Please 
provide feedback on correctness, notable omissions no later than 
2025-11-13 12:00 UTC (and ideally earlier!)

Thanks!

Jonathan

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.

> * Do not use parallelism in hash right semi-joins.

Should this be given additional context?  On it's own, IMHO it's not clear
whether this is a bug fix or something else.

> * Allow nonsuperusers with `SELECT` privileges on a table to use
[`pg_prewarm`](https://www.postgresql.org/docs/current/pgprewarm.html)to prewarm indexes on that table.
 

nitpick: I would probably replace "nonsuperusers" with "users", but it's
correct either way.

-- 
nathan

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?

            regards, tom lane

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?

Ah, yes it is [0].

[0] https://www.postgresql.org/about/news/postgresql-176-1610-1514-1419-1322-and-18-beta-3-released-3118/

-- 
nathan

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

On Mon, Nov 10, 2025 at 08:57:32PM -0500, Jonathan S. Katz wrote:
> 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.

Maybe "Avoid returning duplicate rows from hash right semi-joins"?

-- 
nathan

On 11/11/25 5:14 PM, Nathan Bossart wrote:
> On Mon, Nov 10, 2025 at 08:57:32PM -0500, Jonathan S. Katz wrote:
>> 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.
> 
> Maybe "Avoid returning duplicate rows from hash right semi-joins"?

I adopted this phrasing. Thanks!

Jonathan