postgresql.index.scans
Index scans initiatedDimensions:None
Interface Metrics (5)
Dimensions:None
Dimensions:None
Sources
Technical Annotations (20)
Configuration Parameters (1)
default_statistics_targetrecommended: 1000CLI Commands (8)
CLUSTER identities_identity USING index_name;remediationALTER TABLE identities_identity ALTER COLUMN email_domain SET STATISTICS 10000;diagnosticVACUUM ANALYZE identities_identity;remediationALTER TABLE your_table ALTER COLUMN status SET STATISTICS 500;remediationSELECT indexrelname AS index_name, relname AS table_name, idx_scan AS times_used, pg_size_pretty(pg_relation_size(indexrelid)) AS index_size FROM pg_stat_user_indexes WHERE idx_scan = 0 AND indexrelid NOT IN (SELECT indexrelid FROM pg_index WHERE indisprimary) ORDER BY pg_relation_size(indexrelid) DESC;diagnosticDROP INDEX index_name;remediationEXPLAIN ANALYZE SELECT * FROM table_name WHERE column_name = 'value'diagnosticSELECT schemaname, relname AS table_name, seq_scan, idx_scan, n_tup_ins AS inserts, n_tup_upd AS updates, n_tup_del AS deletes, n_dead_tup AS dead_tuples, last_vacuum, last_autovacuum FROM pg_stat_user_tables ORDER BY n_dead_tup DESC;diagnosticTechnical References (11)
correlationconceptLIMIT clauseconceptvarchar_pattern_opscomponentpg_stat_user_indexescomponenthistogramconceptselectivityconceptcardinality estimatesconceptWHERE predicateconceptpg_stat_user_tablescomponentseq_scancomponentidx_scancomponentRelated Insights (6)
Query planner chooses sequential scan over index scan when data distribution is skewedwarning
▸
Index bloat wastes disk space and degrades query performancewarning
▸
Insufficient column statistics cause poor selectivity estimateswarning
▸
Unused indexes waste write performance and storageinfo
▸
Missing indexes force sequential scans on small result setswarning
▸
High sequential scan to index scan ratio indicates missing indexeswarning
▸