Re: First draft of PG 19 release notes

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Subject: Re: First draft of PG 19 release notes
Date: 2026-11-02 21:42:44
Message-ID: CAD21AoCasuD5Fq78ApDitYr86v1cw4YdqeEnEEQzcek27ShTvA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Bruce,

On Tue, Apr 14, 2026 at 6:19 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> I have completed the first draft of the PG 19 release notes:
>
> https://www.postgresql.org/docs/devel/release-19.html
>
> The feature count is 212. The recent average is 200:
>
> https://momjian.us/main/writings/pgsql/missing.pdf#page=3
>
> I will create a wiki page to explain my methods used to create this
> because, someday, someone else will need to do this.
>
> I am traveling April 19 to May 7, so I might not be able to make quick
> adjustments based on feedback. Another committer can handle them, or
> you can wait for me to get to it.

I've pushed a fix (8628df8891a) for how parallel vacuum computes the
cost-based vacuum delay. As I mentioned in the commit message, while
the fix corrects the delay computation, it could make VACUUM with the
PARALLEL option and cost-based delay enabled slower after upgrading to
v19. I think it's worth mentioning this in the release notes so that
users can re-tune the cost-based delay parameters. I've attached the
patch to add the item to the "Migration to Version 19" section. Please
review it.

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

Attachment Content-Type Size
release_note_parallel_vacuum_delay_fix.patch text/x-patch 1.2 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2026-11-02 22:33:21 Re: [RFC] Property-based testing for Postgres
Previous Message Greg Burd 2026-11-02 21:28:10 [RFC] Property-based testing for Postgres