postgresql查看表和索引的情况,判断是否膨胀的操作
项目招商找A5 快速获取精准代理名单
索引膨胀的几个来源:
1 大量删除发生后,导致索引页面稀疏,降低了索引使用效率。
2 PostgresQL 9.0之前的版本,vacuum full 会同样导致索引页面稀疏。
3 长时间运行的事务,禁止vacuum对表的清理工作,因而导致页面稀疏状态一直保持。
查看重复索引
SELECT pg_size_pretty(SUM(pg_relation_size(idx))::BIGINT) AS SIZE, (array_agg(idx))[1] AS idx1, (array_agg(idx))[2] AS idx2, (array_agg(idx))[3] AS idx3, (array_agg(idx))[4] AS idx4FROM (SELECT indexrelid::regclass AS idx, (indrelid::text ||E'\n'|| indclass::text ||E'\n'|| indkey::text ||E'\n'|| COALESCE(indexprs::text,'')||E'\n' || COALESCE(indpred::text,'')) AS KEYFROM pg_index) subGROUP BY KEY HAVING COUNT(*)>1ORDER BY SUM(pg_relation_size(idx)) DESC;
表的大小和表中索引个数
SELECTt.tablename,indexname,c.reltuples AS num_rows,pg_size_pretty(pg_relation_size(quote_ident(t.tablename)::text)) AS table_size,pg_size_pretty(pg_relation_size(quote_ident(indexrelname)::text)) AS index_size,CASE WHEN indisunique THEN 'Y' ELSE 'N'END AS UNIQUE,idx_scan AS number_of_scans,idx_tup_read AS tuples_read,idx_tup_fetch AS tuples_fetchedFROM pg_tables tLEFT OUTER JOIN pg_class c ON t.tablename=c.relnameLEFT OUTER JOIN( SELECT c.relname AS ctablename, ipg.relname AS indexname, x.indnatts AS number_of_columns, 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 fooON t.tablename = foo.ctablenameWHERE t.schemaname='public'ORDER BY 1,2;
获取每个表的行数,索引和一些关于这些索引的信息(比较详细)
SELECTpg_class.relname,pg_size_pretty(pg_class.reltuples::BIGINT) AS rows_in_bytes,pg_class.reltuples AS num_rows,COUNT(indexname) AS number_of_indexes,CASE WHEN x.is_unique = 1 THEN 'Y' ELSE 'N'END AS UNIQUE,SUM(CASE WHEN number_of_columns = 1 THEN 1 ELSE 0 END) AS single_column,SUM(CASE WHEN number_of_columns IS NULL THEN 0 WHEN number_of_columns = 1 THEN 0 ELSE 1 END) AS multi_columnFROM pg_namespace LEFT OUTER JOIN pg_class ON pg_namespace.oid = pg_class.relnamespaceLEFT OUTER JOIN (SELECT indrelid, MAX(CAST(indisunique AS INTEGER)) AS is_unique FROM pg_index GROUP BY indrelid) x ON pg_class.oid = x.indrelidLEFT OUTER JOIN( SELECT c.relname AS ctablename, ipg.relname AS indexname, x.indnatts AS number_of_columns FROM pg_index x JOIN pg_class c ON c.oid = x.indrelid JOIN pg_class ipg ON ipg.oid = x.indexrelid )AS fooON pg_class.relname = foo.ctablenameWHERE pg_namespace.nspname='public'AND pg_class.relkind = 'r'GROUP BY pg_class.relname, pg_class.reltuples, x.is_uniqueORDER BY 2;
补充:postgresql查看表膨胀
查看表膨胀(对所有表产进行膨胀率排序)
SQL文如下:
SELECTschemaname||'.'||relname as table_name,pg_size_pretty(pg_relation_size(schemaname||'.'||relname)) as table_size,n_dead_tup,n_live_tup,round(n_dead_tup * 100 / (n_live_tup + n_dead_tup),2) AS dead_tup_ratioFROMpg_stat_all_tablesWHEREn_dead_tup >= 1000ORDER BY dead_tup_ratio DESCLIMIT 10;
文章来源:脚本之家
来源地址:https://www.jb51.net/article/204333.htm
尊敬的看官您对postgresql查看表和索引的情况,判断是否膨胀的操作有什么看法呢?互联网品牌制作专家愿与您共同探讨!版权声明:本文内容由互联网用户自发贡献,该文观点仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容, 请加微信号oem365 举报,一经查实,本站将立刻删除。上一篇: PostgreSQL表膨胀监控案例(精确计算) 返 回 下一篇:PostgreSQL的外部数据封装器fdw用法