EXPLAIN Quirks: PostgreSQL's Missing Index Usage Details
PostgreSQL's EXPLAIN command contains detailed information about many aspect of a query's execution plan. But one particular set of information is curiously absent.
Query plans, index strategy, and the planner's stranger decisions — written by the
people building IndeX-Ray. No fluff, lots of EXPLAIN.
PostgreSQL's EXPLAIN command contains detailed information about many aspect of a query's execution plan. But one particular set of information is curiously absent.
Today we introduce IndeX-Ray™ which is a simple, intuitive, and powerful way to visualize indexes inside of databases!
Indexes tell databases where to find information that it is looking for. Under the right circumstances, the index can save the database even more time by providing the requested information directly.
Indexes are the core component that drive efficient database performance. How do they do it?
Indexes are incredible, but not magical. There are times when they should not be used. Forcing a database to use one when it doesn't naturally want to could cause performance to get worse.
New posts on Postgres performance, plus the occasional changelog. No drip campaign.
No spam, pinky promise.