当前位置: 首页 > news >正文

postgresql日常维护和检查一-处理表、索引膨胀

对于PostgreSQL处理MVCC(数据文件中新增tuple)的方式;相比其他数据库(Oracle、Mysql)而言;更容易触发表/索引膨胀。因为update操作也会影响表膨胀的问题。PostgreSQL处理的方式是对表autovacuum,vacuum是不会降低水位线。能避免表、索引膨胀。vacuum full,reindex才会降低水位线。

当然通过update带来的表膨胀的情况还可以接受;PostgreSQL处理的方式是对表autovacuum。所以能autovacuum的一般不会对表膨胀带来大的影响。影响autovacuum进行对表回收的情况;大致有3种情况

长事务:数据库上有长时间没有提交的事务

SELECT
*
FROM
pg_stat_activity
WHERE
STATE = 'Idle in transaction';
未提交的2pc事务:这个特性是为分布式功能扩展的,非分布式的架构默认是关闭的

SELECT
gid,
PREPARED,
OWNER,
DATABASE,
TRANSACTION AS xmin
FROM
pg_prepared_xacts
ORDER BY
age( TRANSACTION ) DESC
复制槽:逻辑复制、流复制都会有复制槽;复制槽的作用:通过记录复制的当前位置;保证备库、订阅端未接收到的数据不会在主库删除。但是废弃的复制槽会影响表的vacuum。这个是危害最大的

SELECT
slot_name,
slot_type,
DATABASE,
xmin
FROM
pg_replication_slots
ORDER BY
age( xmin ) DESC;
如何知道表膨胀呢?即监控

安装

create extension pgstattuple;

查看前5的膨胀表

select oid::regclass,(pgstattuple(oid)).* from pg_class where relkind='r' order by free_space desc limit 5 offset 0;

查看前5的索引

select oid::regclass,(pgstattuple(oid)).* from pg_class where relkind='i' order by free_space desc limit 5 offset 0;
-- 表
SELECT
current_database() AS db, schemaname, tablename, reltuples::bigint AS tups, relpages::bigint AS pages, otta,
ROUND(CASE WHEN otta=0 OR sml.relpages=0 OR sml.relpages=otta THEN 0.0 ELSE sml.relpages/otta::numeric END,1) AS tbloat,
CASE WHEN relpages < otta THEN 0 ELSE relpages::bigint - otta END AS wastedpages,
CASE WHEN relpages < otta THEN 0 ELSE bs(sml.relpages-otta)::bigint END AS wastedbytes,
CASE WHEN relpages < otta THEN $$0 bytes$$::text ELSE (bs
(relpages-otta))::bigint || $$ bytes$$ END AS wastedsize,
iname, ituples::bigint AS itups, ipages::bigint AS ipages, iotta,
ROUND(CASE WHEN iotta=0 OR ipages=0 OR ipages=iotta THEN 0.0 ELSE ipages/iotta::numeric END,1) AS ibloat,
CASE WHEN ipages < iotta THEN 0 ELSE ipages::bigint - iotta END AS wastedipages,
CASE WHEN ipages < iotta THEN 0 ELSE bs(ipages-iotta) END AS wastedibytes,
CASE WHEN ipages < iotta THEN $$0 bytes$$ ELSE (bs
(ipages-iotta))::bigint || $$ bytes$$ END AS wastedisize,
CASE WHEN relpages < otta THEN
CASE WHEN ipages < iotta THEN 0 ELSE bs(ipages-iotta::bigint) END
ELSE CASE WHEN ipages < iotta THEN bs
(relpages-otta::bigint)
ELSE bs(relpages-otta::bigint + ipages-iotta::bigint) END
END AS totalwastedbytes
FROM (
SELECT
nn.nspname AS schemaname,
cc.relname AS tablename,
COALESCE(cc.reltuples,0) AS reltuples,
COALESCE(cc.relpages,0) AS relpages,
COALESCE(bs,0) AS bs,
COALESCE(CEIL((cc.reltuples
((datahdr+ma-
(CASE WHEN datahdr%ma=0 THEN ma ELSE datahdr%ma END))+nullhdr2+4))/(bs-20::float)),0) AS otta,
COALESCE(c2.relname,$$?$$) AS iname, COALESCE(c2.reltuples,0) AS ituples, COALESCE(c2.relpages,0) AS ipages,
COALESCE(CEIL((c2.reltuples(datahdr-12))/(bs-20::float)),0) AS iotta -- very rough approximation, assumes all cols
FROM
pg_class cc
JOIN pg_namespace nn ON cc.relnamespace = nn.oid AND nn.nspname <> $$information_schema$$
LEFT JOIN
(
SELECT
ma,bs,foo.nspname,foo.relname,
(datawidth+(hdr+ma-(case when hdr%ma=0 THEN ma ELSE hdr%ma END)))::numeric AS datahdr,
(maxfracsum
(nullhdr+ma-(case when nullhdr%ma=0 THEN ma ELSE nullhdr%ma END))) AS nullhdr2
FROM (
SELECT
ns.nspname, tbl.relname, hdr, ma, bs,
SUM((1-coalesce(null_frac,0))coalesce(avg_width, 2048)) AS datawidth,
MAX(coalesce(null_frac,0)) AS maxfracsum,
hdr+(
SELECT 1+count(
)/8
FROM pg_stats s2
WHERE null_frac<>0 AND s2.schemaname = ns.nspname AND s2.tablename = tbl.relname
) AS nullhdr
FROM pg_attribute att
JOIN pg_class tbl ON att.attrelid = tbl.oid
JOIN pg_namespace ns ON ns.oid = tbl.relnamespace
LEFT JOIN pg_stats s ON s.schemaname=ns.nspname
AND s.tablename = tbl.relname
AND s.inherited=false
AND s.attname=att.attname,
(
SELECT
(SELECT current_setting($$block_size$$)::numeric) AS bs,
CASE WHEN SUBSTRING(SPLIT_PART(v, $$ $$, 2) FROM $$#"[0-9]+.[0-9]+#"%$$ for $$#$$)
IN ($$8.0$$,$$8.1$$,$$8.2$$) THEN 27 ELSE 23 END AS hdr,
CASE WHEN v ~ $$mingw32$$ OR v ~ $$64-bit$$ THEN 8 ELSE 4 END AS ma
FROM (SELECT version() AS v) AS foo
) AS constants
WHERE att.attnum > 0 AND tbl.relkind=$$r$$
GROUP BY 1,2,3,4,5
) AS foo
) AS rs
ON cc.relname = rs.relname AND nn.nspname = rs.nspname
LEFT JOIN pg_index i ON indrelid = cc.oid
LEFT JOIN pg_class c2 ON c2.oid = i.indexrelid
) AS sml order by wastedbytes desc limit 5
-- 索引
SELECT
current_database() AS db, schemaname, tablename, reltuples::bigint AS tups, relpages::bigint AS pages, otta,
ROUND(CASE WHEN otta=0 OR sml.relpages=0 OR sml.relpages=otta THEN 0.0 ELSE sml.relpages/otta::numeric END,1) AS tbloat,
CASE WHEN relpages < otta THEN 0 ELSE relpages::bigint - otta END AS wastedpages,
CASE WHEN relpages < otta THEN 0 ELSE bs(sml.relpages-otta)::bigint END AS wastedbytes,
CASE WHEN relpages < otta THEN $$0 bytes$$::text ELSE (bs
(relpages-otta))::bigint || $$ bytes$$ END AS wastedsize,
iname, ituples::bigint AS itups, ipages::bigint AS ipages, iotta,
ROUND(CASE WHEN iotta=0 OR ipages=0 OR ipages=iotta THEN 0.0 ELSE ipages/iotta::numeric END,1) AS ibloat,
CASE WHEN ipages < iotta THEN 0 ELSE ipages::bigint - iotta END AS wastedipages,
CASE WHEN ipages < iotta THEN 0 ELSE bs(ipages-iotta) END AS wastedibytes,
CASE WHEN ipages < iotta THEN $$0 bytes$$ ELSE (bs
(ipages-iotta))::bigint || $$ bytes$$ END AS wastedisize,
CASE WHEN relpages < otta THEN
CASE WHEN ipages < iotta THEN 0 ELSE bs(ipages-iotta::bigint) END
ELSE CASE WHEN ipages < iotta THEN bs
(relpages-otta::bigint)
ELSE bs(relpages-otta::bigint + ipages-iotta::bigint) END
END AS totalwastedbytes
FROM (
SELECT
nn.nspname AS schemaname,
cc.relname AS tablename,
COALESCE(cc.reltuples,0) AS reltuples,
COALESCE(cc.relpages,0) AS relpages,
COALESCE(bs,0) AS bs,
COALESCE(CEIL((cc.reltuples
((datahdr+ma-
(CASE WHEN datahdr%ma=0 THEN ma ELSE datahdr%ma END))+nullhdr2+4))/(bs-20::float)),0) AS otta,
COALESCE(c2.relname,$$?$$) AS iname, COALESCE(c2.reltuples,0) AS ituples, COALESCE(c2.relpages,0) AS ipages,
COALESCE(CEIL((c2.reltuples(datahdr-12))/(bs-20::float)),0) AS iotta -- very rough approximation, assumes all cols
FROM
pg_class cc
JOIN pg_namespace nn ON cc.relnamespace = nn.oid AND nn.nspname <> $$information_schema$$
LEFT JOIN
(
SELECT
ma,bs,foo.nspname,foo.relname,
(datawidth+(hdr+ma-(case when hdr%ma=0 THEN ma ELSE hdr%ma END)))::numeric AS datahdr,
(maxfracsum
(nullhdr+ma-(case when nullhdr%ma=0 THEN ma ELSE nullhdr%ma END))) AS nullhdr2
FROM (
SELECT
ns.nspname, tbl.relname, hdr, ma, bs,
SUM((1-coalesce(null_frac,0))coalesce(avg_width, 2048)) AS datawidth,
MAX(coalesce(null_frac,0)) AS maxfracsum,
hdr+(
SELECT 1+count(
)/8
FROM pg_stats s2
WHERE null_frac<>0 AND s2.schemaname = ns.nspname AND s2.tablename = tbl.relname
) AS nullhdr
FROM pg_attribute att
JOIN pg_class tbl ON att.attrelid = tbl.oid
JOIN pg_namespace ns ON ns.oid = tbl.relnamespace
LEFT JOIN pg_stats s ON s.schemaname=ns.nspname
AND s.tablename = tbl.relname
AND s.inherited=false
AND s.attname=att.attname,
(
SELECT
(SELECT current_setting($$block_size$$)::numeric) AS bs,
CASE WHEN SUBSTRING(SPLIT_PART(v, $$ $$, 2) FROM $$#"[0-9]+.[0-9]+#"%$$ for $$#$$)
IN ($$8.0$$,$$8.1$$,$$8.2$$) THEN 27 ELSE 23 END AS hdr,
CASE WHEN v ~ $$mingw32$$ OR v ~ $$64-bit$$ THEN 8 ELSE 4 END AS ma
FROM (SELECT version() AS v) AS foo
) AS constants
WHERE att.attnum > 0 AND tbl.relkind=$$r$$
GROUP BY 1,2,3,4,5
) AS foo
) AS rs
ON cc.relname = rs.relname AND nn.nspname = rs.nspname
LEFT JOIN pg_index i ON indrelid = cc.oid
LEFT JOIN pg_class c2 ON c2.oid = i.indexrelid
) AS sml order by wastedibytes desc limit 5
使用pg_reorg|pg_repack、pg_squeeze或者vacuum full可以回收膨胀的空间

--http://www.postgres.cn/news/viewone/1/224

索引膨胀会影响查询效率;处理索引膨胀的方法:重建索引

创建新索引
create index CONCURRENTLY new_index
删除旧索引
drop index new_index
或者
reindex index ... CONCURRENTLY
合理调整autovacuum参数;

1、 设置合适的autovacuum_vacuum_scale_factor, 大表如果频繁的有更新或删除和插入操作, 建议设置较小的autovacuum_vacuum_scale_factor来降低浪费空间,加快对表的vacuum操作频率
对更新频繁的表,单独调整
alter table tablename set (autovacuum_vacuum_scale_factor=0.05);

2、设置表的fillfactor;对频繁更新的表;调低fillfactor参数
alter table tablename set (fillfactor = 85)

http://www.jsqmd.com/news/348975/

相关文章:

  • 聚氨酯筛板加工厂哪家品牌好用,江苏地区高性价比选择有哪些 - 工业品牌热点
  • 2026销售管理系统盘点:10款全链路CRM+供应链系统横向对比 - 毛毛鱼的夏天
  • 百考通AI:开题报告智能生成专家,让学术起点不再迷茫!
  • 2026CRM系统排行榜:9 大主流品牌数字化工具核心能力横评 - 毛毛鱼的夏天
  • 百考通AI:智能问卷设计,让市场调研与用户洞察变得简单高效!
  • 传统成果转化困局如何破?生态协同机制助力学术产业双赢
  • catman Easy/AP | 应变四分之一桥温度补偿的理论与实践
  • PPT 批量转图片:在 Web 预览中实现翻页效果(C#/VB.NET) - E
  • 百考通AI:毕业论文写作的智能“加速器”,轻松搞定学术难题!
  • 构建成果转化新生态,赋能高校科研创新
  • 科技成果转化的未来之路——构建区域创新生态新范式
  • 百考通AI:论文降重与去AI痕迹的智能解决方案,让毕业无忧!
  • 谈河北政润研发能力,陕西山西用户口碑好的产品推荐 - mypinpai
  • 2026年评价高的助眠等离子发生器/除尘除味等离子发生器厂家推荐及选择参考 - 行业平台推荐
  • 高校科研转化新引擎:构建科技成果转化的数智化未来
  • java分支与循环
  • ceph缓存分层
  • 百考通AI:权威AIGC检测,为学术诚信保驾护航
  • 一文读懂 Java 主流编译器:特性、场景与选择指南
  • 传统成果转化困局破解之道——高校科研生态协同机制的创新实践
  • ZooKeeper 是什么?看完这篇,社招面试再也不虚
  • 高校科研转化新路径:生态协同机制助力学术产业双赢
  • 查重太高?AI检测又红了?别emo!百考通「降重+降AI」来给你论文“一键真人化+学术柔光滤镜”啦~
  • 有效运用长尾关键词优化SEO策略的实用指南
  • 查重太高?AI检测又亮红灯?别慌!百考通「降重+降AI」来给你论文“一键真人化+学术柔光滤镜”啦~
  • 无人机视角道路坑洞检测数据集VOC+YOLO格式58张1类别
  • 五大学习方法
  • 查重飙高?AI检测又拉警报?别慌!百考通「降重+降AI」来给你论文“一键真人化+学术柔光”啦~
  • 基于随机森林模型的轴承剩余寿命预测MATLAB实现!
  • 查重爆红?AI检测报警?别emo!百考通「降重+降AI」来给你论文“一键真人认证+学术柔光”啦~