Re: 2026-08-13 release announcement draft

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

"Jonathan S. Katz" <jkatz(at)postgresql(dot)org> writes:
> On 8/9/26 2:28 PM, Tom Lane wrote:
>> 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.

That's an artifact of my release note process: the initial draft in
the latest stable branch documents everything, then after I copy that
text into the older branches I remove anything that's not relevant to
the latest branch.

> 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).

I did remove it in a4c41bbcc, which is why you don't see it anymore.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2026-08-09 20:19:02 btoidsortsupport issue
Previous Message Jonathan S. Katz 2026-08-09 18:53:57 Re: 2026-08-13 release announcement draft