Re: First draft of PG 19 release notes

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: First draft of PG 19 release notes
Date: 2026-06-25 02:57:47
Message-ID: 6D50BAF9-0586-420C-AFAC-CCDB61EF694A@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Jun 18, 2026, at 09:45, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> On Wed, Jun 17, 2026 at 09:34:38PM -0400, Bruce Momjian wrote:
>> On Thu, Jun 18, 2026 at 10:29:47AM +0900, Fujii Masao wrote:
>>> On Wed, Apr 15, 2026 at 10:19 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>>>>
>>>> I have completed the first draft of the PG 19 release notes:
>>>
>>> Thanks for working on the release note!
>>>
>>> Reduce lock level of ALTER DOMAIN ... VALIDATE CONSTRAINT to match
>>> ALTER TABLE ... VALIDATE CONSTRAINT (Jian He) §
>>>
>>> I reverted this change at commit 64797ad97d6, so could you please
>>> remove this item from the release notes?
>>
>> Oh, I missed that one, removed, thanks.
>
> Ah, I missed it because it happened today and I was only current as of
> yesterday. I have now updated to be current as of today.
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
> EDB https://enterprisedb.com
>
> Do not let urgent matters crowd out time for investment in the future.

Hi, Bruce,

I noticed a typo in the item about “2026-03-27 [d7965d65f] Add rudimentary table prioritization to autovacuum”. The line is quite long, so I attached a diff file for your convenience.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

Attachment Content-Type Size
fix-typo-about-d7965d65f.diff application/octet-stream 1.4 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chengpeng Yan 2026-06-25 03:12:13 Re: Improve UNION's output rowcount estimate
Previous Message Chao Li 2026-06-25 02:44:23 doc: fix pg_stat_autovacuum_scores threshold wording