EXPLAIN - Insights
- Disk Sort
When a Sort operation spills to disk due to low work_mem settings - Expensive
When particular nodes are more expensive than others in a plan - Hash Batches
When a Hash operation spilles to disk due to low work_mem settings - Inefficient Index
When an index is inefficient because it's loading too much data and then filters rows without an index - I/O Heavy
When most plan I/O happens in just a few plan nodes - Large Offset
When OFFSET is used for pagination, instead of an efficient method such as keyset-based pagination - Lossy Bitmaps
Bitmap Heap Scan that utilizes a lossy bitmap due to low work_mem - Mis-Estimate
The Postgres planner mis-estimated the number of rows a particular plan node returns - Slow Scan
Sequential Scan that removed a significant number of rows (an index would have helped to avoid this) - Stale Stats
The table referenced has not had anANALYZErun recently (potentially leading to inefficient plans)
Couldn't find what you were looking for or want to talk about something specific?
Start a conversation with us →