Re: pgsql: Release notes for 18.4, 17.10, 16.14, 15.18, 14.23.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org, Kirill Reshke <reshkekirill(at)gmail(dot)com>
Subject: Re: pgsql: Release notes for 18.4, 17.10, 16.14, 15.18, 14.23.
Date: 2026-05-11 13:40:29
Message-ID: 1747127.1778506829@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On May 11, 2026 12:40:00 PM GMT+02:00, Kirill Reshke <reshkekirill(at)gmail(dot)com> wrote:
>> On Sun, 10 May 2026, 21:08 Tom Lane, <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Release notes for 18.4, 17.10, 16.14, 15.18, 14.23.

>> Hi! Is there any reason this is not pushed to 18 stable?

> Already was a few days ago:
> https://git.postgresql.org/pg/commitdiff/122adefc94a4dc4e97b4fd5c3328e7dc5b58ebd0

Yeah. I used my usual log message for this pass at the release notes,
even though there happened to be no changes since Friday for the v18
branch. (That's quite unusual: usually there are more commits, or
bits to remove because the newest-stable branch doesn't have a given
bug, or edits suggested by the community.) So that's why the
commit message mentions 18.4 even though v18 didn't change.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2026-05-11 16:12:21 pgsql: Remove test cases for field overflows in intarray and ltree.
Previous Message Noah Misch 2026-05-11 12:19:41 pgsql: Avoid overflow in size calculations in formatting.c.