Re: PostgreSQL 19 beta 1 release announcement draft

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Cc: PostgreSQL Advocacy <pgsql-advocacy(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL 19 beta 1 release announcement draft
Date: 2026-06-03 17:13:36
Message-ID: 431d188c-85e3-4bce-b5c4-cad574d72d2b@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

(for individual replies, I'll be commenting on specific areas that have
some form of follow-up; otherwise I'm accepting/rejecting suggestions.
Thanks!)

On 5/29/26 12:45 PM, Greg Sabino Mullane wrote:

>
> > that lets table scans mark pages as visible
>
> This sentence trips me up mentally each time I read it. Not sure of a
> solution.

I took another read - I expanded on it a bit but made it sound less
PostgreSQL inside knowledge specific:

==
PostgreSQL 19 further enhances vacuum with a new strategy that can
automatically reduce future vacuuming work by using making optimizations
while queries are executing.
==

> > making it easier to use logical replication for use cases like upgrades
>
> making it easier for upgrades

Opted for:

==
In PostgreSQL 19, logical replication now replicates sequence values,
simplifying tasks like online upgrades.
==

Thanks!

Jonathan

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Jonathan S. Katz 2026-06-03 17:20:04 Re: PostgreSQL 19 beta 1 release announcement draft
Previous Message Miaolai Zhou 2026-06-02 14:36:06 Re: PostgreSQL 19 beta 1 release announcement draft