Philip McClarence
Author ProfileClaim This Author Profile
Prove ownership by publishing #HashtagPLUS and this profile link on your author page or an article under your byline. A moderator or admin will review the request before it merges into your real HashtagPLUS username.
🌐 dev.toSource
From Dev.to - database: PostgreSQL Query Anti-Patterns and Common Mistakes
🌐 dev.toSource
From Dev.to - database: PostgreSQL Aggregate and Window Function Tuning
🌐 dev.toSource
From Dev.to - sql: PostgreSQL Join Optimization: Nested Loop, Hash, and Merge
🌐 dev.toSource
Most PostgreSQL performance work is wasted because it starts from the wrong end. Someone notices a slow query, skim-reads EXPLAIN, pattern-matches to "missing index," adds one, and moves on. Sometimes that works. Often it doesn't — and when it doesn't, the next attempt is usually
🌐 dev.toSource
Every PostgreSQL performance conversation eventually lands on a question that sounds trivial: what does this EXPLAIN mean? The output is almost readable. There are node names in English, numbers that look familiar, and enough structure that you can guess at the intent. But if you