Re: 2026-08-13 release announcement draft

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: 2026-08-13 release announcement draft
Date: 2026-08-09 18:53:57
Message-ID: 41844025-6bbb-420e-8516-bff3f54efebb@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/9/26 2:28 PM, Tom Lane wrote:
> "Jonathan S. Katz" <jkatz(at)postgresql(dot)org> writes:
>> Please see attached draft of the 2026-08-13 release announcement, which
>> includes fixes both for the quarterly update release and the PG19 Beta.
>> Please check for accuracy, glaring omissions, confusing phrases, and typos.
>
> One of the bigger-ticket bugs is:
>
> * Fix a self-deadlock that could occur while replaying WAL generated by an older
> minor version. This regression, introduced in the previous set of minor
> releases, could cause a standby server following a primary running an older
> minor version to become stuck.
>
> Contrary to what you say at the top of the list, this doesn't affect
> v18, only v14-v16. I think this one is definitely important enough
> to mention, but maybe put it separately from the main list?
The list was generated from my build of the v18 release notes, and this
was in there - though I found the commit message that did confirm it's
only v14-16.

Agree it deserves a special callout (I also remember this issue when it
was reported) - but do you want to remove it also from the 18.5 release
notes? (I checked release-18.sgml and couldn't find it).

Jonathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-08-09 19:03:57 Re: 2026-08-13 release announcement draft
Previous Message Tom Lane 2026-08-09 18:28:48 Re: 2026-08-13 release announcement draft