postgresql.heap_blocks_read
Heap blocks read from diskDimensions:None
Interface Metrics (3)
Dimensions:None
Dimensions:None
Sources
Technical Annotations (20)
Configuration Parameters (1)
fillfactorrecommended: lower than 100CLI Commands (6)
EXPLAIN (ANALYZE, BUFFERS) SELECT ... WHERE x = ? ORDER BY y LIMIT n;diagnosticCREATE INDEX ON table(filter_column, order_column);remediationEXPLAIN (ANALYZE, BUFFERS) SELECT ...diagnosticCREATE INDEX idx_orders_status_created ON orders (status, created_at DESC);remediationEXPLAIN ANALYZEdiagnosticCREATE INDEX CONCURRENTLY ON cities (country_code) INCLUDE (id, latitude, longitude);remediationTechnical References (13)
multi-column indexconceptIndex Scan BackwardconceptcardinalityconceptSeq ScanconceptEXPLAIN ANALYZEcomponentBuffers: shared readconceptHOT updatesconceptpg_repackcomponentpg_squeezecomponentcovering indexconceptIndex Only ScanconceptINCLUDEconceptHeap FetchesconceptRelated Insights (4)
Inefficient sort-then-limit requires fetching all rows before sortingwarning
▸
Sequential scan on large table causes excessive disk reads and slow query executioncritical
▸
Data locality degradation causes excessive buffer reads over timewarning
▸
Covering indexes reduce heap access but require clean visibility mapinfo
▸