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

相关文章

PostgreSQL简介及实战应用

《PostgreSQL简介及实战应用》PostgreSQL是一种功能强大的开源关系型数据库管理系统,以其稳定性、高性能、扩展性和复杂查询能力在众多项目中得到广泛应用,本文将从基础概念讲起,逐步深入到高... 目录前言1. PostgreSQL基础1.1 PostgreSQL简介1.2 基础语法1.3 数据库

Android 缓存日志Logcat导出与分析最佳实践

《Android缓存日志Logcat导出与分析最佳实践》本文全面介绍AndroidLogcat缓存日志的导出与分析方法,涵盖按进程、缓冲区类型及日志级别过滤,自动化工具使用,常见问题解决方案和最佳实... 目录android 缓存日志(Logcat)导出与分析全攻略为什么要导出缓存日志?按需过滤导出1. 按

Linux中的HTTPS协议原理分析

《Linux中的HTTPS协议原理分析》文章解释了HTTPS的必要性:HTTP明文传输易被篡改和劫持,HTTPS通过非对称加密协商对称密钥、CA证书认证和混合加密机制,有效防范中间人攻击,保障通信安全... 目录一、什么是加密和解密?二、为什么需要加密?三、常见的加密方式3.1 对称加密3.2非对称加密四、

MySQL中读写分离方案对比分析与选型建议

《MySQL中读写分离方案对比分析与选型建议》MySQL读写分离是提升数据库可用性和性能的常见手段,本文将围绕现实生产环境中常见的几种读写分离模式进行系统对比,希望对大家有所帮助... 目录一、问题背景介绍二、多种解决方案对比2.1 原生mysql主从复制2.2 Proxy层中间件:ProxySQL2.3

Oracle迁移PostgreSQL隐式类型转换配置指南

《Oracle迁移PostgreSQL隐式类型转换配置指南》Oracle迁移PostgreSQL时因类型差异易引发错误,需通过显式/隐式类型转换、转换关系管理及冲突处理解决,并配合验证测试确保数据一致... 目录一、问题背景二、解决方案1. 显式类型转换2. 隐式转换配置三、维护操作1. 转换关系管理2.

python使用Akshare与Streamlit实现股票估值分析教程(图文代码)

《python使用Akshare与Streamlit实现股票估值分析教程(图文代码)》入职测试中的一道题,要求:从Akshare下载某一个股票近十年的财务报表包括,资产负债表,利润表,现金流量表,保存... 目录一、前言二、核心知识点梳理1、Akshare数据获取2、Pandas数据处理3、Matplotl

python panda库从基础到高级操作分析

《pythonpanda库从基础到高级操作分析》本文介绍了Pandas库的核心功能,包括处理结构化数据的Series和DataFrame数据结构,数据读取、清洗、分组聚合、合并、时间序列分析及大数据... 目录1. Pandas 概述2. 基本操作:数据读取与查看3. 索引操作:精准定位数据4. Group

MySQL中EXISTS与IN用法使用与对比分析

《MySQL中EXISTS与IN用法使用与对比分析》在MySQL中,EXISTS和IN都用于子查询中根据另一个查询的结果来过滤主查询的记录,本文将基于工作原理、效率和应用场景进行全面对比... 目录一、基本用法详解1. IN 运算符2. EXISTS 运算符二、EXISTS 与 IN 的选择策略三、性能对比

MySQL 内存使用率常用分析语句

《MySQL内存使用率常用分析语句》用户整理了MySQL内存占用过高的分析方法,涵盖操作系统层确认及数据库层bufferpool、内存模块差值、线程状态、performance_schema性能数据... 目录一、 OS层二、 DB层1. 全局情况2. 内存占js用详情最近连续遇到mysql内存占用过高导致

深度解析Nginx日志分析与499状态码问题解决

《深度解析Nginx日志分析与499状态码问题解决》在Web服务器运维和性能优化过程中,Nginx日志是排查问题的重要依据,本文将围绕Nginx日志分析、499状态码的成因、排查方法及解决方案展开讨论... 目录前言1. Nginx日志基础1.1 Nginx日志存放位置1.2 Nginx日志格式2. 499