PostgreSQL Query Rewriting Techniques The previous articles in this series covered performance problems you fix by adding indexes, restructuring joins, or tuning memory. This one is about the queries where the plan is "fine" — every node is doing something reasonable — but the query itself is asking the wrong question, producing unnecessarily large intermediate results or forcing the planner dow
This section is the map for the rest of the book. The five stages introduced in the 1.1 chapter overview (parse, analyze/rewrite, plan, portal, execute) are traced here through the actual code: which functions implement each stage, and in what order they get called. The mechanics of each of the five stages are unpacked in later chapters. Here, only the skeleton matters: how a backend starts up, ho
PostgreSQL Internals · Chapter 1 Query Processing Suppose a client sends SELECT * FROM users WHERE id = 1. The path that single line travels before coming back as a result row is longer than you might expect. Inside the PostgreSQL backend, that SQL goes through a five-stage pipeline. Backend entry and dispatch. The backend receives the message from the client and decides which processing path it s
I've been burned by AI testing tools before. They promise "zero configuration, just point at your app," then spend 20 minutes generating test cases that fail on the login screen. So when I tried TestSprite, I went in skeptical — and came out with a more nuanced take than I expected. Here's my honest dev review after running it on a real project, with specific attention to how it handles locale-sen
Testing tools come and go. Most promise "zero code, full coverage." TestSprite actually made me stop and pay attention — for good reasons and a few frustrating ones. Background: What I Was Testing I was working on a mid-scale web application — a financial dashboard that aggregates payment data for Indonesian SMEs. The app handles IDR (Indonesian Rupiah) currency formatting, date displays in the dd
TL;DR: TestSprite is the most intuitive AI testing platform I've used. The test execution is solid, the dashboard is clean, and the automation works. But if you're building globally, watch out for locale handling gaps. Here's what I found after running it on a real project. I tested TestSprite on a SaaS project with users across 15+ countries. The onboarding was refreshingly simple — no complex se
When you're building a global app, localization testing is the unglamorous but critical work. Most devs skip it until production breaks in a timezone 12 hours ahead. I used TestSprite on a real project last week and found exactly why that matters. I tested a payment dashboard against TestSprite's locale suite. The app handles USD transactions with dates, timezone-aware reporting, and currency form
I spent 3 hours with TestSprite last week, integrating it into a Claude Code workflow. Here's my honest review: it's the missing piece in agentic development that actually delivers on its promise. What TestSprite Is (And Isn't) TestSprite is an autonomous AI testing agent that sits between your AI code generator and production. It doesn't replace your test suite. It verifies that AI-generated code