use*_*057 1 postgresql indexing database-performance
我运行此查询来检查我的数据库中是否有一些未使用的索引。
select
t.tablename AS "relation",
indexname,
c.reltuples AS num_rows,
pg_relation_size(quote_ident(t.tablename)::text) AS table_size,
pg_relation_size(quote_ident(indexrelname)::text) AS index_size,
idx_scan AS number_of_scans,
idx_tup_read AS tuples_read,
idx_tup_fetch AS tuples_fetched
FROM pg_tables t
LEFT OUTER JOIN pg_class c ON t.tablename=c.relname
LEFT OUTER JOIN
( SELECT c.relname AS ctablename, ipg.relname AS indexname, x.indnatts AS number_of_columns, psai.idx_scan, idx_tup_read, idx_tup_fetch, indexrelname, indisunique FROM pg_index x
JOIN pg_class c ON c.oid = x.indrelid
JOIN pg_class ipg ON ipg.oid = x.indexrelid
JOIN pg_stat_all_indexes psai ON x.indexrelid = psai.indexrelid )
AS foo
ON t.tablename = foo.ctablename
WHERE t.schemaname='public'
and idx_scan = 0
ORDER BY
--1,2
--6
5 desc
;
Run Code Online (Sandbox Code Playgroud)
我得到了很多行,其中这些字段全部为零:
number_of_scans,
tuples_read,
tuples_fetched
Run Code Online (Sandbox Code Playgroud)
这是否意味着我可以放弃它们?该元数据有可能已经过时吗?我怎样才能检查它?
我使用的是 9.6 版本的 Postgres
您的查询错过了一些不需要扫描索引的用途:
它们强制执行主键、唯一和排除约束
它们影响统计数据收集(对于“表达索引”)
这是我的博客文章中的黄金标准查询:
SELECT s.schemaname,
s.relname AS tablename,
s.indexrelname AS indexname,
pg_relation_size(s.indexrelid) AS index_size
FROM pg_catalog.pg_stat_user_indexes s
JOIN pg_catalog.pg_index i ON s.indexrelid = i.indexrelid
WHERE s.idx_scan = 0 -- has never been scanned
AND 0 <>ALL (i.indkey) -- no index column is an expression
AND NOT EXISTS -- does not enforce a constraint
(SELECT 1 FROM pg_catalog.pg_constraint c
WHERE c.conindid = s.indexrelid)
ORDER BY pg_relation_size(s.indexrelid) DESC;
Run Code Online (Sandbox Code Playgroud)
由于统计数据已重置并且可以安全删除,因此显示在那里的任何内容都没有被使用过。
有一些注意事项:
必须运行统计信息收集(查找“统计信息收集器”进程并查看日志中是否有有关“过时统计信息”的警告)
针对您的生产数据库运行查询
如果您的程序在许多站点上运行,请在所有站点上尝试(不同的用户有不同的使用模式)