Nothing here yet.
Nothing here yet.
1d ago · 13 min read · If you've ever watched a query go from 30 ms to 30 seconds after a data load — without a single line of SQL changing — you've been on the wrong side of a join-strategy flip. Joins are the part of PostgreSQL that's most sensitive to statistics. A 10× ...
Join discussion2d ago · 8 min read · PostgreSQL Index Usage and Optimization If you've spent any time tuning PostgreSQL, you've hit the same frustrating moment: you added an index, you're sure it should be used, and the plan still shows a sequential scan. Or the index is used, but the q...
Join discussion5d ago · 16 min read · If you've ever pasted an EXPLAIN plan into a Slack channel and hoped a teammate would tell you what it meant, this article is for you. Plans are almost readable — node names in English, numbers that look familiar — and that almost-readability is exac...
Join discussionApr 22 · 4 min read · PostgreSQL Parallel Query: Configuration & Performance Tuning I was helping a team optimize their reporting pipeline. Their aggregation queries against a 100M-row table were taking 30+ seconds each. They had a 32-core server with plenty of RAM. When ...
Join discussion
Apr 21 · 4 min read · PostgreSQL Point-in-Time Recovery with pgBackRest A few months ago, a startup I advise had a junior developer accidentally run a migration that dropped and recreated a table -- in production instead of staging. They had pg_dump backups every 12 hours...
Join discussion
