PostgreSQL 19 was released today. pgEdge packages for it are available the same day across all of our supported deployments - including Spock, where PG 19 support is already available. I have been testing the release candidates for a few weeks, so here is what I think matters most to DBAs and teams. replaces and , and with the option it rebuilds a bloated table without blocking reads and writes. In my own test, inserts kept running at about 2,000 a second with no failed transactions while a bloated table was rebuilt in under a second. It needs a primary key or replica identity index, and it is not MVCC safe for transactions that started before the swap. Shaun Thomas wrote a blog on the topic - give it a read for more detail. gets the biggest changes for anyone running replicated clusters. Sequences can now be published with and synced with , which removes the manual step from migrations and upgrades. Logical replication can also be turned on without a restart when is replica. Subscriptions get for better conflict detection, and publications can leave tables out with ., autovacuum can now use parallel workers on indexes and ranks tables with a scoring system, so the ones that need it most go first. The and extensions let you steer the planner and keep a plan you trust. The new command gives read-your-writes consistency on standbys. are worth knowing. is faster on text and CSV input, can now write JSON, and lets a load continue past bad values. For monitoring, is now on by default, there is a new view, and the wraparound warning now starts at 100 million transactions instead of 40 million.
Backend
Ahsan Hadi: PostgreSQL 19 is Here: Worth the Wait
Planet PostgreSQL0 views
Source:https://postgr.es/p/9CT
PreviousApple’s head of camera and Photos software has retired, per reportNextBlockchain system could secure cross-border renewable energy and carbon certificate trade
Related posts
What a Garry's Mod Backdoor Actually Looks Like (and How to Spot One)
0dev.to Security

Mozilla measured 25M Firefox users: a handful of browser signals do most of the fingerprinting
0dev.to Security

15 CVE Findings, 0 Real: Scanner Output in Code Review, Checked by Blind Judges
0dev.to Security
Why a Remote Image Renders but Canvas Pixel Access Fails
0dev.to Security
A dead man's switch that survives an internet shutdown: inside Kengele's deadline engine in Go
0dev.to Security
228 bytes that can't be read, faked or told apart: Kengele's wire format and Nostr gift wraps in Go
0dev.to Security