PostgreSQL 19
The 19th major version of the PostgreSQL database, introducing new features and internal format changes. Its release schedule has been delayed due to regression fixes and compatibility verification.
Core Facts
Timeline (last 90 days)
The Hacker News discussion thread about PostgreSQL 19 received 328 points.
PostgreSQL 19's release documentation has appeared on the official site at /docs/release/19.0/
PostgreSQL 19 has officially reached GA (General Availability).
A new version does not mean it is suitable to go straight into production; teams should make a comprehensive judgment based on their own stability requirements as well as Lakebase's support period and upgrade path for that version.
Lakebase completed adaptation and rollout on the same day PostgreSQL 19 was announced as GA.
PostgreSQL 19 is now available on Lakebase.
PostgreSQL major versions (such as 19) introduce new features, internal format changes, and extension interface adjustments, and upgrades usually need to be validated through paths such as pg_upgrade or logical replication beforehand.
PostgreSQL 19 has been released (generally available).
The main reason for the PostgreSQL 19 release delay is that the team was occupied by a large number of vulnerability reports that needed to be handled, a considerable portion of which came from AI-assisted security research.
PostgreSQL 19 introduced the WAIT FOR LSN command to solve the "read-after-write" consistency problem in read-write splitting architectures.
10 more timeline events
All Facts (14)
The Hacker News discussion had 22 upvotes and 28 comments
80%UnverifiedThe Hacker News discussion thread about PostgreSQL 19 received 328 points.
50%UnverifiedA new version does not mean it is suitable to go straight into production; teams should make a comprehensive judgment based on their own stability requirements as well as Lakebase's support period and upgrade path for that version.
50%UnverifiedPostgreSQL major versions (such as 19) introduce new features, internal format changes, and extension interface adjustments, and upgrades usually need to be validated through paths such as pg_upgrade or logical replication beforehand.
50%UnverifiedThe main reason for the PostgreSQL 19 release delay is that the team was occupied by a large number of vulnerability reports that needed to be handled, a considerable portion of which came from AI-assisted security research.
50%UnverifiedPostgreSQL 19 introduced the WAIT FOR LSN command to solve the "read-after-write" consistency problem in read-write splitting architectures.
50%UnverifiedThe features that remain in PostgreSQL 19 include REPACK CONCURRENTLY, logical replication of sequences, and pg_plan_advice.
50%UnverifiedTom Lane once said that if PostgreSQL 19 shipped SQL/PGQ anyway, the resulting production bugs might not be fixed until PostgreSQL 20.
50%UnverifiedAccording to Peter Eisentraut's own account, LLM-assisted review did speed up defect exposure, but the PostgreSQL 19 delay also involves the knock-on adjustments caused by feature reverts during the beta cycle.
50%UnverifiedPostgreSQL 19's release documentation has appeared on the official site at /docs/release/19.0/
50%UnverifiedPostgreSQL 19 is now available on Lakebase.
50%UnverifiedLakebase completed adaptation and rollout on the same day PostgreSQL 19 was announced as GA.
50%UnverifiedPostgreSQL 19 has officially reached GA (General Availability).
50%UnverifiedPostgreSQL 19 has been released (generally available).
50%