PostgreSQL 19 Beta 3

A dated reading of what is claimed, reported, and independently verified in the current evidence.

Current reading

Readiness band and full integer triple

AI-assisted assembly · derived results

Readiness band

Ready

Primary summary from verified readiness

Evidence strength Strong

Decision

Human editorial judgment · 2026-08-20

Track; not yet

Why: Rule #30 keeps Postgres remote-only on two approved managed projects; a pre-RC beta with explicitly unstable behaviors/APIs and 14 unresolved open items is not a migration candidate today, but the same announcement's CVE batch (14 of the 28 CVEs rated 8.8, including a privilege-escalation-adjacent psql \unrestrict flaw) is operationally relevant right now regardless of PG19 status.
Next: Re-check at GA (official roadmap targets September 2026); do not point any managed Postgres project at PG19 until RC clears the 14 open items and a stable 19.x minor exists. Separately and immediately actionable: confirm which of the 28 CVEs fixed in the paired 18.6/17.11/16.15/15.19/14.24 releases (2026-08-13) apply to whatever PG major/minor Supabase currently runs for the soft/trust projects, and schedule that patch independent of PG19 tracking.

Constraints

No named blocker is present in the current public projection.

Evidence summary

AI-assisted assembly

Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.

Publication record

Initial public reading