Re: 2026-05-14 release announcement draft

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Robert Treat <rob(at)xzilla(dot)net>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: 2026-05-14 release announcement draft
Date: 2026-05-12 01:18:19
Message-ID: b1894ed2-7b04-4302-bcf0-b8d62af5844f@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 5/11/26 4:52 PM, Robert Treat wrote:
> On Sun, May 10, 2026 at 9:44 PM Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
>>
>> Hi,
>>
>> I've attached a draft of the 2026-05-14 release announcement. Please
>> provide feedback on corrections, notable omissions, typos, etc. no later
>> than 2026-05-14 12:00 UTC (though preferable earlier sooner! :)
>>
>
> Generally LGTM, some minor comments / thoughts below...
>
> * I thought this one "Improve the planner's ability to apply partition
> pruning to more cases." was worded more like a feature enhancement
> rather than a fix of some kind, but I didn't see the corresponding
> commit, so not sure what improvement to suggest.

It was this one:

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8e8b2bef7

> * I'd probably rewrite this one:

I went with:

> Ensure that free space map changes are persisted during recovery.
> This could have performance ramifications on a standby server after
promotion.

Thanks,

Jonathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2026-05-12 01:35:06 Re: [Bug][patch]: After dropping the last label from a property graph element, invoking pg_get_propgraphdef() triggers an assertion failure
Previous Message Junwang Zhao 2026-05-12 00:57:09 Re: [SQL/PGQ] Early pruning for GRAPH_TABLE path generation