PostgreSQL 19 Beta 1 release announcement draft

On Fri, May 29, 2026 at 5:23 AM Jonathan S. Katz <jkatz@postgresql.org> wrote:

Hi,

Attached is the draft of the PostgreSQL 19 Beta 1 release announcement.
Please review for accuracy (e.g. are features described correctly? Did I
miss a revert), recommendations on additions or glaring omissions,
structure, etc.

Please provide feedback no later than June 4, 2026 12:00 UTC (though
preferably earlier!)

Hi Jonathan, thanks for preparing it. Three thoughts, not sure You agree with
them, but while reading this I had these reactions:

I would recommend moving 'pg_plan_advice' a bit higher, as at least here we've
got quite volume of users asking for it often in emergencies, but also lack of
this feature also caused some not to migrate, because PG was missing it
earlier.

Also 64-bit MultiXactOffset is not directly called, but can be huge win for
some, maybe something like "64-bit MultiXactOffset greatly reduces the risk
of MultiXact member-space exhaustion: it prevents emergency anti-wraparound
vacuums previously caused by highly concurrent workloads involving FKs."

Perhaps also "GROUP BY ALL" could be listed as well under `Developer
Experience`.

-J.

On Fri, May 29, 2026 at 6:23 AM Jonathan S. Katz <jkatz@postgresql.org>
wrote:

Hi,

Attached is the draft of the PostgreSQL 19 Beta 1 release announcement.
Please review for accuracy (e.g. are features described correctly? Did I
miss a revert), recommendations on additions or glaring omissions,
structure, etc.

Please provide feedback no later than June 4, 2026 12:00 UTC (though
preferably earlier!)

I'd phrase the jsonpath part like this:
This release extends string processing capabilities in jsonpath with the
addition of lower(), upper(), initcap(), replace(), split_part(), and the
trim() family of functions

I'd also add GROUP BY ALL in that paragraph as well.