PostgreSQL源码分析——pg_waldump

2024-06-19 12:04

本文主要是介绍PostgreSQL源码分析——pg_waldump,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

PG中有个可以打印WAL日志信息的工具,pg_waldump,对于开发人员来说,掌握该工具是十分有必要的。

用法

具体用法这里不去详解,可见官网pg_waldump文档。

postgres@slpc:~$ pg_waldump --help
pg_waldump decodes and displays PostgreSQL write-ahead logs for debugging.Usage:pg_waldump [OPTION]... [STARTSEG [ENDSEG]]Options:-b, --bkp-details      output detailed information about backup blocks-e, --end=RECPTR       stop reading at WAL location RECPTR-f, --follow           keep retrying after reaching end of WAL-n, --limit=N          number of records to display-p, --path=PATH        directory in which to find log segment files or adirectory with a ./pg_wal that contains such files(default: current directory, ./pg_wal, $PGDATA/pg_wal)-q, --quiet            do not print any output, except for errors-r, --rmgr=RMGR        only show records generated by resource manager RMGR;use --rmgr=list to list valid resource manager names-s, --start=RECPTR     start reading at WAL location RECPTR-t, --timeline=TLI     timeline from which to read log records(default: 1 or the value used in STARTSEG)-V, --version          output version information, then exit-x, --xid=XID          only show records with transaction ID XID-z, --stats[=record]   show statistics instead of records(optionally, show per-record statistics)-?, --help             show this help, then exit

具体的,我们举一个例子:

postgres=# create table t1(a int);
CREATE TABLEpostgres=# select pg_current_wal_lsn();pg_current_wal_lsn 
--------------------0/1696C78
(1 row)
-- 插入一条数据
postgres=# insert into t1 values(1);
INSERT 0 1
postgres=# select pg_current_wal_insert_lsn();pg_current_wal_insert_lsn 
---------------------------0/1696D18
(1 row)
postgres=# select txid_current();txid_current 
--------------735
(1 row)-- 查看WAL日志
postgres@slpc:~/pgsql$ pg_waldump -p pgdata/pg_wal/ -s 0/1696C78 -e 0/1696D18
-- 插入一条数据,堆表, 事务ID 735   
rmgr: Heap        len (rec/tot):     59/    59, tx:        734, lsn: 0/01696C78, prev 0/01696C40, desc: INSERT+INIT off 1 flags 0x00, blkref #0: rel 1663/13010/16384 blk 0 
rmgr: Transaction len (rec/tot):     34/    34, tx:        734, lsn: 0/01696CB8, prev 0/01696C78, desc: COMMIT 2023-09-23 10:58:39.915785 CST
rmgr: Standby     len (rec/tot):     54/    54, tx:          0, lsn: 0/01696CE0, prev 0/01696CB8, desc: RUNNING_XACTS nextXid 735 latestCompletedXid 733 oldestRunningXid 734; 1 xacts: 734-- 设置wal_debug = on
postgres=# set wal_debug = on;
SET
postgres=# select pg_current_wal_lsn();pg_current_wal_lsn 
--------------------0/1696E28
(1 row)postgres=# insert into t1 values(2);
LOG:  INSERT @ 0/1696EC0:  - Heap/INSERT: off 2 flags 0x00
LOG:  INSERT @ 0/1696EE8:  - Transaction/COMMIT: 2023-09-23 11:27:25.399199+08
LOG:  xlog flush request 0/1696EE8; write 0/1696E28; flush 0/1696E28
INSERT 0 1
postgres=# select pg_current_wal_lsn();pg_current_wal_lsn 
--------------------0/1696F20
(1 row)postgres@slpc:~/pgsql$ pg_waldump -p pgdata/pg_wal/ -s 0/1696E28 -e 0/1696F20
rmgr: Heap        len (rec/tot):     54/   150, tx:        736, lsn: 0/01696E28, prev 0/01696DF0, desc: INSERT off 2 flags 0x00, blkref #0: rel 1663/13010/16384 blk 0 FPW
rmgr: Transaction len (rec/tot):     34/    34, tx:        736, lsn: 0/01696EC0, prev 0/01696E28, desc: COMMIT 2023-09-23 11:27:25.399199 CST
rmgr: Standby     len (rec/tot):     50/    50, tx:          0, lsn: 0/01696EE8, prev 0/01696EC0, desc: RUNNING_XACTS nextXid 737 latestCompletedXid 736 oldestRunningXid 737
pg_waldump源码分析

pg_waldump的源码比较简单,在src/bin/pg_waldump中, 执行pg_waldump -p pgdata/pg_wal/ -s 0/1696E28 -e 0/1696F20进行调试。

main(int argc, char **argv)
--> XLogReaderAllocate(WalSegSz, waldir,XL_ROUTINE(.page_read = WALDumpReadPage,.segment_open = WALDumpOpenSegment, .segment_close = WALDumpCloseSegment), &private);// 因为我们是读wal日志的一个范围,从起点到终点,所以,这里第1步要做的就是先找到起始的wal日志记录
--> XLogFindNextRecord(xlogreader_state, private.startptr);for (;;){// 开始读取后续WAL日志/* try to read the next record */record = XLogReadRecord(xlogreader_state, &errormsg);/* perform any per-record work */if (!config.quiet){if (config.stats == true)XLogDumpCountRecord(&config, &stats, xlogreader_state);elseXLogDumpDisplayRecord(&config, xlogreader_state);}/* check whether we printed enough */config.already_displayed_records++;if (config.stop_after_records > 0 &&config.already_displayed_records >= config.stop_after_records)break;}
--> XLogReaderFree(xlogreader_state);	

更详细的代码可以查看:

int main(int argc, char **argv)
{uint32		xlogid;uint32		xrecoff;XLogReaderState *xlogreader_state;XLogDumpPrivate private;XLogDumpConfig config;XLogDumpStats stats;XLogRecord *record;XLogRecPtr	first_record;private.timeline = 1;private.startptr = InvalidXLogRecPtr;     // 起点private.endptr = InvalidXLogRecPtr;       // 终点private.endptr_reached = false;while ((option = getopt_long(argc, argv, "be:fn:p:qr:s:t:x:z", long_options, &optindex)) != -1){switch (option){case 'e':if (sscanf(optarg, "%X/%X", &xlogid, &xrecoff) != 2){pg_log_error("could not parse end WAL location \"%s\"",optarg);goto bad_argument;}private.endptr = (uint64) xlogid << 32 | xrecoff;break;case 's':if (sscanf(optarg, "%X/%X", &xlogid, &xrecoff) != 2){pg_log_error("could not parse start WAL location \"%s\"",optarg);goto bad_argument;}elseprivate.startptr = (uint64) xlogid << 32 | xrecoff;break;// ...}}// .../* done with argument parsing, do the actual work *//* we have everything we need, start reading */// 初始化XLogReader,分配读取所需的内存空间xlogreader_state = XLogReaderAllocate(WalSegSz, waldir, XL_ROUTINE(.page_read = WALDumpReadPage,.segment_open = WALDumpOpenSegment,.segment_close = WALDumpCloseSegment), &private);/* first find a valid recptr to start from */// 找到第一个lsn >= startptr的有效日志记录first_record = XLogFindNextRecord(xlogreader_state, private.startptr);if (first_record == InvalidXLogRecPtr)fatal_error("could not find a valid record after %X/%X",LSN_FORMAT_ARGS(private.startptr));/** Display a message that we're skipping data if `from` wasn't a pointer* to the start of a record and also wasn't a pointer to the beginning of* a segment (e.g. we were used in file mode).*/if (first_record != private.startptr &&XLogSegmentOffset(private.startptr, WalSegSz) != 0)printf(ngettext("first record is after %X/%X, at %X/%X, skipping over %u byte\n","first record is after %X/%X, at %X/%X, skipping over %u bytes\n",(first_record - private.startptr)),LSN_FORMAT_ARGS(private.startptr),LSN_FORMAT_ARGS(first_record),(uint32) (first_record - private.startptr));for (;;){/* try to read the next record */record = XLogReadRecord(xlogreader_state, &errormsg);if (!record){if (!config.follow || private.endptr_reached)break;else{pg_usleep(1000000L);	/* 1 second */continue;}}/* apply all specified filters */if (config.filter_by_rmgr != -1 &&config.filter_by_rmgr != record->xl_rmid)continue;if (config.filter_by_xid_enabled &&config.filter_by_xid != record->xl_xid)continue;/* perform any per-record work */if (!config.quiet){if (config.stats == true)XLogDumpCountRecord(&config, &stats, xlogreader_state);elseXLogDumpDisplayRecord(&config, xlogreader_state);}/* check whether we printed enough */config.already_displayed_records++;if (config.stop_after_records > 0 &&config.already_displayed_records >= config.stop_after_records)break;}if (config.stats == true && !config.quiet)XLogDumpDisplayStats(&config, &stats);if (errormsg)fatal_error("error in WAL record at %X/%X: %s",LSN_FORMAT_ARGS(xlogreader_state->ReadRecPtr),errormsg);XLogReaderFree(xlogreader_state);return EXIT_SUCCESS;bad_argument:fprintf(stderr, _("Try \"%s --help\" for more information.\n"), progname);return EXIT_FAILURE;
}

参考文档:
pg_waldump

这篇关于PostgreSQL源码分析——pg_waldump的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



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

相关文章

Spring Boot Interceptor的原理、配置、顺序控制及与Filter的关键区别对比分析

《SpringBootInterceptor的原理、配置、顺序控制及与Filter的关键区别对比分析》本文主要介绍了SpringBoot中的拦截器(Interceptor)及其与过滤器(Filt... 目录前言一、核心功能二、拦截器的实现2.1 定义自定义拦截器2.2 注册拦截器三、多拦截器的执行顺序四、过

C++ scoped_ptr 和 unique_ptr对比分析

《C++scoped_ptr和unique_ptr对比分析》本文介绍了C++中的`scoped_ptr`和`unique_ptr`,详细比较了它们的特性、使用场景以及现代C++推荐的使用`uni... 目录1. scoped_ptr基本特性主要特点2. unique_ptr基本用法3. 主要区别对比4. u

Nginx内置变量应用场景分析

《Nginx内置变量应用场景分析》Nginx内置变量速查表,涵盖请求URI、客户端信息、服务器信息、文件路径、响应与性能等类别,这篇文章给大家介绍Nginx内置变量应用场景分析,感兴趣的朋友跟随小编一... 目录1. Nginx 内置变量速查表2. 核心变量详解与应用场景3. 实际应用举例4. 注意事项Ng

Java多种文件复制方式以及效率对比分析

《Java多种文件复制方式以及效率对比分析》本文总结了Java复制文件的多种方式,包括传统的字节流、字符流、NIO系列、第三方包中的FileUtils等,并提供了不同方式的效率比较,同时,还介绍了遍历... 目录1 背景2 概述3 遍历3.1listFiles()3.2list()3.3org.codeha

Nginx分布式部署流程分析

《Nginx分布式部署流程分析》文章介绍Nginx在分布式部署中的反向代理和负载均衡作用,用于分发请求、减轻服务器压力及解决session共享问题,涵盖配置方法、策略及Java项目应用,并提及分布式事... 目录分布式部署NginxJava中的代理代理分为正向代理和反向代理正向代理反向代理Nginx应用场景

Redis中的有序集合zset从使用到原理分析

《Redis中的有序集合zset从使用到原理分析》Redis有序集合(zset)是字符串与分值的有序映射,通过跳跃表和哈希表结合实现高效有序性管理,适用于排行榜、延迟队列等场景,其时间复杂度低,内存占... 目录开篇:排行榜背后的秘密一、zset的基本使用1.1 常用命令1.2 Java客户端示例二、zse

Redis中的AOF原理及分析

《Redis中的AOF原理及分析》Redis的AOF通过记录所有写操作命令实现持久化,支持always/everysec/no三种同步策略,重写机制优化文件体积,与RDB结合可平衡数据安全与恢复效率... 目录开篇:从日记本到AOF一、AOF的基本执行流程1. 命令执行与记录2. AOF重写机制二、AOF的

MyBatis Plus大数据量查询慢原因分析及解决

《MyBatisPlus大数据量查询慢原因分析及解决》大数据量查询慢常因全表扫描、分页不当、索引缺失、内存占用高及ORM开销,优化措施包括分页查询、流式读取、SQL优化、批处理、多数据源、结果集二次... 目录大数据量查询慢的常见原因优化方案高级方案配置调优监控与诊断总结大数据量查询慢的常见原因MyBAT

分析 Java Stream 的 peek使用实践与副作用处理方案

《分析JavaStream的peek使用实践与副作用处理方案》StreamAPI的peek操作是中间操作,用于观察元素但不终止流,其副作用风险包括线程安全、顺序混乱及性能问题,合理使用场景有限... 目录一、peek 操作的本质:有状态的中间操作二、副作用的定义与风险场景1. 并行流下的线程安全问题2. 顺

MyBatis/MyBatis-Plus同事务循环调用存储过程获取主键重复问题分析及解决

《MyBatis/MyBatis-Plus同事务循环调用存储过程获取主键重复问题分析及解决》MyBatis默认开启一级缓存,同一事务中循环调用查询方法时会重复使用缓存数据,导致获取的序列主键值均为1,... 目录问题原因解决办法如果是存储过程总结问题myBATis有如下代码获取序列作为主键IdMappe