Read After Write | Scaling Postgres 433

In this episode of Scaling Postgres, we see examples of using WAIT FOR in PG 19 for handling read after write, local NVME vs block store, new system views and the ambiguity of NULL.

Content Discussed

• Read your own writes, off the primary
• POSETTE Talk Recap - Postgres Isn't Slow. Your Storage Is
• New system views in PostgreSQL 19
• Postgres Calculations and the Ambiguity of NULL
• LinkedIn Live: All right, so you inherited a bad database...
• pg-catalog-almanac
• Getting Ready for PostgreSQL 19
• How Fast Should You Patch Production PostgreSQL?
• From the Trenches: My Path Through Postgres
• Migration files and Git do not mix
• pgwatch v6: dashboards reimagined, and a reaper that doesn't choke
• The Dump That Breaks Its Own Restore
• That’s how Postgres met Django!
• How to Calculate Fillfactor for Your Tables
• Loading the Northwinds Database Into PostgreSQL with DBeaver
• When AI Takes Action, What Proves What Actually Happened?
• Reading Table Bloat Before It Reads You
• Time-Series Cardinality: Why One More Indexed Column Costs More Than a Million More Rows
• Why a 40-Year-Old Database Is Still Winning in the AI Era
• How Companion.energy Reduced Query Latency 25x and Compressed Terabytes to Gigabytes with Tiger Cloud
• 14,000x Faster Planning for LIMIT Queries on Hypertables
• What is a Neki router?
• How one connection kills a database
• SQL Server to Aurora PostgreSQL conversion with AI agents for AWS DMS
• Fix circular role dependencies before upgrading Amazon RDS and Amazon Aurora PostgreSQL
• CORTO’s billion-scale legal semantic search with Aurora PostgreSQL pgvector

YouTube Video

Podcast Audio