Postgresql源码(35)vacuum freeze起始位点逻辑分析

2023-10-19 12:10

本文主要是介绍Postgresql源码(35)vacuum freeze起始位点逻辑分析,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

查询指令

https://blog.csdn.net/jackgo73/article/details/122700702


SELECT n.nspname as "Schema", c.relname as "Name", c.relfrozenxid,age(c.relfrozenxid) 
FROM pg_catalog.pg_class c
LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
WHERE c.relkind IN ('r','')
AND n.nspname <> 'information_schema' AND n.nspname !~ '^pg_toast'
AND pg_catalog.pg_table_is_visible(c.oid)
ORDER BY c.relfrozenxid::text::bigint DESC;select datname,age(datfrozenxid),2^31-age(datfrozenxid) age_remain from pg_database order by age(datfrozenxid) desc;
select current_database(),rolname,nspname,relkind,relname,age(relfrozenxid),2^31-age(relfrozenxid) age_remain from pg_authid t1 join pg_class t2 on t1.oid=t2.relowner join pg_namespace t3 on t2.relnamespace=t3.oid where t2.relkind in ($$t$$,$$r$$) order by age(relfrozenxid) desc limit 5;select datname,usename,query,xact_start,now()-xact_start xact_duration,query_start,now()-query_start query_duration,state from pg_stat_activity where state<>$$idle$$ and (backend_xid is not null or backend_xmin is not null) and now()-xact_start > interval $$30 min$$ order by xact_start;
select name,statement,prepare_time,now()-prepare_time,parameter_types,from_sql from pg_prepared_statements where now()-prepare_time > interval $$30 min$$ order by prepare_time;

关键参数

系统级


# (final模式默认两亿,把回收xid位点limit设为oldestXmin,然后把limit之前的全部freeze,同时开始告警)
autovacuum_freeze_max_age = 200000000      # 如果表的事务ID年龄大于该值, 即使未开启autovacuum也会强制触发FREEZE, 并告警Preventing Transaction ID Wraparound Failures# (lazy模式默认五千万,把回收xid位点limit设为oldestXmin减五千万,回收垃圾元组的同时顺便freeze)
vacuum_freeze_min_age = 50000000           # 手动或自动垃圾回收时, 如果记录的事务ID年龄大于该值, 将被FREEZE    # (eager模式默认一亿五千万,把回收xid位点limit设为oldestXmin减一亿五千万,按vm按需扫页面然后freeze)
vacuum_freeze_table_age = 150000000        # 手动垃圾回收时, 如果表的事务ID年龄大于该值, 将触发FREEZE. 该参数的上限值为 %95 autovacuum_freeze_max_age    # 组合事务ID限制,同上述配置。
autovacuum_multixact_freeze_max_age = 400000000      # 如果表的并行事务ID年龄大于该值, 即使未开启autovacuum也会强制触发FREEZE, 并告警Preventing Transaction ID Wraparound Failures 
vacuum_multixact_freeze_min_age = 5000000            # 手动或自动垃圾回收时, 如果记录的并行事务ID年龄大于该值, 将被FREEZE    
vacuum_multixact_freeze_table_age = 150000000        # 手动垃圾回收时, 如果表的并行事务ID年龄大于该值, 将触发FREEZE. 该参数的上限值为 %95 autovacuum_multixact_freeze_max_age    # 其他配置
autovacuum_vacuum_cost_delay       # 自动垃圾回收时, 每轮回收周期后的一个休息时间, 主要防止垃圾回收太耗资源. -1 表示沿用vacuum_cost_delay的设置    
autovacuum_vacuum_cost_limit       # 自动垃圾回收时, 每轮回收周期设多大限制, 限制由vacuum_cost_page_hit,vacuum_cost_page_missvacuum_cost_page_dirty参数以及周期内的操作决定. -1 表示沿用vacuum_cost_limit的设置    
vacuum_cost_delay                  # 手动垃圾回收时, 每轮回收周期后的一个休息时间, 主要防止垃圾回收太耗资源.    
vacuum_cost_limit                  # 手动垃圾回收时, 每轮回收周期设多大限制, 限制由vacuum_cost_page_hit,vacuum_cost_page_missvacuum_cost_page_dirty参数以及周期内的操作决定.    

表级

# 系统级:autovacuum_freeze_max_age = 500000000
# 表级分段配置:
alter table t set (autovacuum_freeze_max_age=210000000);
alter table t set (autovacuum_freeze_max_age=220000000);
alter table t set (autovacuum_freeze_max_age=230000000);
..

计算cutoff位点

起始freeze的位点


void
vacuum_set_xid_limits(Relation rel,int freeze_min_age,int freeze_table_age,int multixact_freeze_min_age,int multixact_freeze_table_age,TransactionId *oldestXmin,TransactionId *freezeLimit,TransactionId *xidFullScanLimit,MultiXactId *multiXactCutoff,MultiXactId *mxactFullScanLimit)
{int			freezemin;int			mxid_freezemin;int			effective_multixact_freeze_max_age;TransactionId limit;TransactionId safeLimit;MultiXactId oldestMxact;MultiXactId mxactLimit;MultiXactId safeMxactLimit;/** We can always ignore processes running lazy vacuum.  This is because we* use these values only for deciding which tuples we must keep in the* tables.  Since lazy vacuum doesn't write its XID anywhere, it's safe to* ignore it.  In theory it could be problematic to ignore lazy vacuums in* a full vacuum, but keep in mind that only one vacuum process can be* working on a particular table at any time, and that each vacuum is* always an independent transaction.*/*oldestXmin =TransactionIdLimitedForOldSnapshots(GetOldestXmin(rel, PROCARRAY_FLAGS_VACUUM), rel);Assert(TransactionIdIsNormal(*oldestXmin));/** Determine the minimum freeze age to use: as specified by the caller, or* vacuum_freeze_min_age, but in any case not more than half* autovacuum_freeze_max_age, so that autovacuums to prevent XID* wraparound won't occur too frequently.*/// vacuum_freeze_min_age这个值太大了会被置为autovacuum_freeze_max_age的1/2。// 配的太大了会频繁的做freezefreezemin = freeze_min_age;if (freezemin < 0)freezemin = vacuum_freeze_min_age;freezemin = Min(freezemin, autovacuum_freeze_max_age / 2);Assert(freezemin >= 0);/** Compute the cutoff XID, being careful not to generate a "permanent" XID*/limit = *oldestXmin - freezemin;if (!TransactionIdIsNormal(limit))limit = FirstNormalTransactionId;/** If oldestXmin is very far back (in practice, more than* autovacuum_freeze_max_age / 2 XIDs old), complain and force a minimum* freeze age of zero.*/safeLimit = ReadNewTransactionId() - autovacuum_freeze_max_age;if (!TransactionIdIsNormal(safeLimit))safeLimit = FirstNormalTransactionId;

下面判断逻辑会根据情况调整freeze起始位点
在这里插入图片描述

	if (TransactionIdPrecedes(limit, safeLimit)){ereport(WARNING,(errmsg("oldest xmin is far in the past"),errhint("Close open transactions soon to avoid wraparound problems.")));limit = *oldestXmin;}*freezeLimit = limit;/** Compute the multixact age for which freezing is urgent.  This is* normally autovacuum_multixact_freeze_max_age, but may be less if we are* short of multixact member space.*/effective_multixact_freeze_max_age = MultiXactMemberFreezeThreshold();/** Determine the minimum multixact freeze age to use: as specified by* caller, or vacuum_multixact_freeze_min_age, but in any case not more* than half effective_multixact_freeze_max_age, so that autovacuums to* prevent MultiXact wraparound won't occur too frequently.*/mxid_freezemin = multixact_freeze_min_age;if (mxid_freezemin < 0)mxid_freezemin = vacuum_multixact_freeze_min_age;mxid_freezemin = Min(mxid_freezemin,effective_multixact_freeze_max_age / 2);Assert(mxid_freezemin >= 0);/* compute the cutoff multi, being careful to generate a valid value */oldestMxact = GetOldestMultiXactId();mxactLimit = oldestMxact - mxid_freezemin;if (mxactLimit < FirstMultiXactId)mxactLimit = FirstMultiXactId;safeMxactLimit =ReadNextMultiXactId() - effective_multixact_freeze_max_age;if (safeMxactLimit < FirstMultiXactId)safeMxactLimit = FirstMultiXactId;if (MultiXactIdPrecedes(mxactLimit, safeMxactLimit)){ereport(WARNING,(errmsg("oldest multixact is far in the past"),errhint("Close open transactions with multixacts soon to avoid wraparound problems.")));/* Use the safe limit, unless an older mxact is still running */if (MultiXactIdPrecedes(oldestMxact, safeMxactLimit))mxactLimit = oldestMxact;elsemxactLimit = safeMxactLimit;}*multiXactCutoff = mxactLimit;if (xidFullScanLimit != NULL){int			freezetable;Assert(mxactFullScanLimit != NULL);/** Determine the table freeze age to use: as specified by the caller,* or vacuum_freeze_table_age, but in any case not more than* autovacuum_freeze_max_age * 0.95, so that if you have e.g nightly* VACUUM schedule, the nightly VACUUM gets a chance to freeze tuples* before anti-wraparound autovacuum is launched.*/freezetable = freeze_table_age;if (freezetable < 0)freezetable = vacuum_freeze_table_age;freezetable = Min(freezetable, autovacuum_freeze_max_age * 0.95);Assert(freezetable >= 0);/** Compute XID limit causing a full-table vacuum, being careful not to* generate a "permanent" XID.*/limit = ReadNewTransactionId() - freezetable;if (!TransactionIdIsNormal(limit))limit = FirstNormalTransactionId;*xidFullScanLimit = limit;/** Similar to the above, determine the table freeze age to use for* multixacts: as specified by the caller, or* vacuum_multixact_freeze_table_age, but in any case not more than* autovacuum_multixact_freeze_table_age * 0.95, so that if you have* e.g. nightly VACUUM schedule, the nightly VACUUM gets a chance to* freeze multixacts before anti-wraparound autovacuum is launched.*/freezetable = multixact_freeze_table_age;if (freezetable < 0)freezetable = vacuum_multixact_freeze_table_age;freezetable = Min(freezetable,effective_multixact_freeze_max_age * 0.95);Assert(freezetable >= 0);/** Compute MultiXact limit causing a full-table vacuum, being careful* to generate a valid MultiXact value.*/mxactLimit = ReadNextMultiXactId() - freezetable;if (mxactLimit < FirstMultiXactId)mxactLimit = FirstMultiXactId;*mxactFullScanLimit = mxactLimit;}else{Assert(mxactFullScanLimit == NULL);}
}

验证

实测


select txid_current(); # 14076185# 创建表时relfrozenxid就是当前的事务ID,age=0(currentxid - 创建表时relfrozenxid就是当前的事务ID,age)
create table t9(i int);select age(relfrozenxid),relfrozenxid,relname,pg_size_pretty(pg_total_relation_size(oid)) from pg_class where relname='t9';  age | relfrozenxid | relname | pg_size_pretty 
-----+--------------+---------+----------------1 |     14076186 | t9      | 0 bytesinsert into t9 values (1);
insert into t9 values (2);postgres=# select t_xmin,t_xmax,t_infomask2,t_infomask from heap_page_items(get_raw_page('t9', 0));t_xmin  | t_xmax | t_infomask2 | t_infomask 
----------+--------+-------------+------------14076187 |      0 |           1 |       204814076188 |      0 |           1 |       2048postgres=# select * from pg_stat_user_tables  where relname='t9';
-[ RECORD 1 ]-------+-------
relid               | 135092
schemaname          | public
relname             | t9
seq_scan            | 0
seq_tup_read        | 0
idx_scan            | 
idx_tup_fetch       | 
n_tup_ins           | 2
n_tup_upd           | 0
n_tup_del           | 0
n_tup_hot_upd       | 0
n_live_tup          | 2
n_dead_tup          | 0
n_mod_since_analyze | 2
last_vacuum         |    (执行了,不管清理没清理,都会更新时间)
last_autovacuum     | 
last_analyze        | 
last_autoanalyze    | 
vacuum_count        | 0
autovacuum_count    | 0
analyze_count       | 
autoanalyze_count   | 0【1】启动长事务
【2】启动消耗事务ID:pgbench -M prepared -n -r -P 1 -f ./test.sql -c 32 -j 32 -T 10  # (1)到vacuum_freeze_min_age=5000W时,因为长事务存在,不能freeze。
# (2)不会有报错
# (3)但会提示最老事务的事务ID:oldest xmin: 14076189(就是那个长事务)
vacuum (freeze,verbose) t9;
INFO:  vacuuming "public.t9"
INFO:  "t9": found 0 removable, 2 nonremovable row versions in 1 out of 1 pages
DETAIL:  0 dead row versions cannot be removed yet, oldest xmin: 14076189
There were 0 unused item pointers.
Skipped 0 pages due to buffer pins, 0 frozen pages.
0 pages are entirely empty.
CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s.
VACUUMpostgres=# select age(relfrozenxid),relfrozenxid,relname,pg_size_pretty(pg_total_relation_size(oid)) from pg_class where relname='t9';  age    | relfrozenxid | relname | pg_size_pretty 
----------+--------------+---------+----------------59056502 |     14076189 | t9      | 40 kB# (1)到vacuum_freeze_table_age=15000W时,因为长事务存在,不能freeze。
# (2)不会有报错
# (3)但会提示最老事务的事务ID:oldest xmin: 14076189(就是那个长事务)
postgres=# vacuum (freeze,verbose) t9;
vacuum (freeze,verbose) t9;
INFO:  vacuuming "public.t9"
INFO:  "t9": found 0 removable, 2 nonremovable row versions in 1 out of 1 pages
DETAIL:  0 dead row versions cannot be removed yet, oldest xmin: 14076189
There were 0 unused item pointers.
Skipped 0 pages due to buffer pins, 0 frozen pages.
0 pages are entirely empty.
CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s.
VACUUMpostgres=# select age(relfrozenxid),relfrozenxid,relname,pg_size_pretty(pg_total_relation_size(oid)) from pg_class where relname='t9';  age    | relfrozenxid | relname | pg_size_pretty 
-----------+--------------+---------+----------------153257008 |     14076189 | t9      | 40 kB# (1)到autovacuum_freeze_max_age=20000W时,因为长事务存在,不能freeze。
# (2)开始报警,但是没报错
# (3)但会提示最老事务的事务ID:oldest xmin: 14076189(就是那个长事务)
postgres=# vacuum (freeze,verbose) t9;
WARNING:  oldest xmin is far in the past
HINT:  Close open transactions soon to avoid wraparound problems.
INFO:  vacuuming "public.t9"
INFO:  "t9": found 0 removable, 2 nonremovable row versions in 1 out of 1 pages
DETAIL:  0 dead row versions cannot be removed yet, oldest xmin: 14076189
There were 0 unused item pointers.
Skipped 0 pages due to buffer pins, 0 frozen pages.
0 pages are entirely empty.
CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s.
VACUUM
postgres=# select age(relfrozenxid),relfrozenxid,relname,pg_size_pretty(pg_total_relation_size(oid)) from pg_class where relname='t9';  age    | relfrozenxid | relname | pg_size_pretty 
-----------+--------------+---------+----------------213075933 |     14076189 | t9      | 40 kB

这篇关于Postgresql源码(35)vacuum freeze起始位点逻辑分析的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/239655

相关文章

对postgresql日期和时间的比较

《对postgresql日期和时间的比较》文章介绍了在数据库中处理日期和时间类型时的一些注意事项,包括如何将字符串转换为日期或时间类型,以及在比较时自动转换的情况,作者建议在使用数据库时,根据具体情况... 目录PostgreSQL日期和时间比较DB里保存到时分秒,需要和年月日比较db里存储date或者ti

Go中sync.Once源码的深度讲解

《Go中sync.Once源码的深度讲解》sync.Once是Go语言标准库中的一个同步原语,用于确保某个操作只执行一次,本文将从源码出发为大家详细介绍一下sync.Once的具体使用,x希望对大家有... 目录概念简单示例源码解读总结概念sync.Once是Go语言标准库中的一个同步原语,用于确保某个操

Redis主从/哨兵机制原理分析

《Redis主从/哨兵机制原理分析》本文介绍了Redis的主从复制和哨兵机制,主从复制实现了数据的热备份和负载均衡,而哨兵机制可以监控Redis集群,实现自动故障转移,哨兵机制通过监控、下线、选举和故... 目录一、主从复制1.1 什么是主从复制1.2 主从复制的作用1.3 主从复制原理1.3.1 全量复制

Redis主从复制的原理分析

《Redis主从复制的原理分析》Redis主从复制通过将数据镜像到多个从节点,实现高可用性和扩展性,主从复制包括初次全量同步和增量同步两个阶段,为优化复制性能,可以采用AOF持久化、调整复制超时时间、... 目录Redis主从复制的原理主从复制概述配置主从复制数据同步过程复制一致性与延迟故障转移机制监控与维

Redis连接失败:客户端IP不在白名单中的问题分析与解决方案

《Redis连接失败:客户端IP不在白名单中的问题分析与解决方案》在现代分布式系统中,Redis作为一种高性能的内存数据库,被广泛应用于缓存、消息队列、会话存储等场景,然而,在实际使用过程中,我们可能... 目录一、问题背景二、错误分析1. 错误信息解读2. 根本原因三、解决方案1. 将客户端IP添加到Re

Java汇编源码如何查看环境搭建

《Java汇编源码如何查看环境搭建》:本文主要介绍如何在IntelliJIDEA开发环境中搭建字节码和汇编环境,以便更好地进行代码调优和JVM学习,首先,介绍了如何配置IntelliJIDEA以方... 目录一、简介二、在IDEA开发环境中搭建汇编环境2.1 在IDEA中搭建字节码查看环境2.1.1 搭建步

Redis主从复制实现原理分析

《Redis主从复制实现原理分析》Redis主从复制通过Sync和CommandPropagate阶段实现数据同步,2.8版本后引入Psync指令,根据复制偏移量进行全量或部分同步,优化了数据传输效率... 目录Redis主DodMIK从复制实现原理实现原理Psync: 2.8版本后总结Redis主从复制实

锐捷和腾达哪个好? 两个品牌路由器对比分析

《锐捷和腾达哪个好?两个品牌路由器对比分析》在选择路由器时,Tenda和锐捷都是备受关注的品牌,各自有独特的产品特点和市场定位,选择哪个品牌的路由器更合适,实际上取决于你的具体需求和使用场景,我们从... 在选购路由器时,锐捷和腾达都是市场上备受关注的品牌,但它们的定位和特点却有所不同。锐捷更偏向企业级和专

Spring中Bean有关NullPointerException异常的原因分析

《Spring中Bean有关NullPointerException异常的原因分析》在Spring中使用@Autowired注解注入的bean不能在静态上下文中访问,否则会导致NullPointerE... 目录Spring中Bean有关NullPointerException异常的原因问题描述解决方案总结

python中的与时间相关的模块应用场景分析

《python中的与时间相关的模块应用场景分析》本文介绍了Python中与时间相关的几个重要模块:`time`、`datetime`、`calendar`、`timeit`、`pytz`和`dateu... 目录1. time 模块2. datetime 模块3. calendar 模块4. timeit