随笔 - 404  文章 - 4  评论 - 0  阅读 - 25万

【PgSQL流复制管理】检测主备库复制状态

master:

postgres=# select pid,usename,application_name,client_addr,client_port,backend_start,state,write_lsn,replay_lsn,sync_priority,sync_state from pg_stat_replication;
pid | usename | application_name | client_addr | client_port | backend_start | state | write_lsn | replay_lsn | sync_priority | sync_state
------+---------+------------------+-----------------+-------------+-------------------------------+-----------+--------------+--------------+---------------+------------
1531 | repuser | walreceiver | 100.126.209.202 | 47058 | 2021-12-04 16:07:47.759557+08 | streaming | FCF/3C1D0C70 | FCF/3C1D0C70 | 0 | async
(1 row)

字段state显示的同步状态有:startup(连接中)、catchup(同步中)、streaming(同步);
字段sync_state显示的模式有:async(异步)、sync(同步)、potential(虽然现在是异步模式,但是有可能升级到同步模式)

复制用户

postgres=# select * from pg_user where usesysid='16384';
usename | usesysid | usecreatedb | usesuper | userepl | usebypassrls | passwd | valuntil | useconfig
---------+----------+-------------+----------+---------+--------------+----------+----------+-----------
repuser | 16384 | f | f | t | f | ******** | |
(1 row)

主从延迟:

postgres=# SELECT
postgres-# pg_wal_lsn_diff(A .c1, replay_lsn) /(1024 * 1024) AS slave_latency_MB,
postgres-# pg_wal_lsn_diff(A .c1, sent_lsn) /(1024 * 1024) AS send_latency_MB,
postgres-# pg_wal_lsn_diff(A .c1, flush_lsn) /(1024 * 1024) AS flush_latency_MB,
postgres-# state,
postgres-# backend_start,
postgres-# now()::timestamp with time zone
postgres-# FROM pg_stat_replication, pg_current_wal_lsn() AS A(c1)
postgres-# WHERE client_addr='100.126.209.202' and application_name = 'repuser'
postgres-# ORDER BY slave_latency_MB, send_latency_MB DESC
postgres-# LIMIT 1;
slave_latency_mb | send_latency_mb | flush_latency_mb | state | backend_start | now
------------------+-----------------+------------------+-------+---------------+-----
(0 rows)

数据库活动相关的信息

 postgres=# select datname,client_addr,client_port,backend_start,query_start,query from pg_stat_activity where datname = 'zedb';

 

standby 节点:

postgres=# select pg_is_in_recovery();
pg_is_in_recovery
-------------------
t
(1 row)

postgres=# select pg_last_xact_replay_timestamp();
pg_last_xact_replay_timestamp
-------------------------------
2021-12-05 11:54:06.781469+08
(1 row

 

查看后端进程运行状态

postgres=# select pid,state,CURRENT_TIMESTAMP - least(query_start,xact_start) AS runtime,
substr(query,1,25) AS current_query
from pg_stat_activity
where not pid = pg_backend_pid();
pid | state | runtime | current_query
-------+-------+---------+---------------
826 | | |
828 | | |
827 | | |
10088 | | |
(4 rows)

 

posted on   HelonTian  阅读(479)  评论(0编辑  收藏  举报
编辑推荐:
· SQL Server 2025 AI相关能力初探
· Linux系列:如何用 C#调用 C方法造成内存泄露
· AI与.NET技术实操系列(二):开始使用ML.NET
· 记一次.NET内存居高不下排查解决与启示
· 探究高空视频全景AR技术的实现原理
阅读排行:
· 阿里最新开源QwQ-32B,效果媲美deepseek-r1满血版,部署成本又又又降低了!
· SQL Server 2025 AI相关能力初探
· AI编程工具终极对决:字节Trae VS Cursor,谁才是开发者新宠?
· 开源Multi-agent AI智能体框架aevatar.ai,欢迎大家贡献代码
· Manus重磅发布:全球首款通用AI代理技术深度解析与实战指南
历史上的今天:
2020-12-05 问题处理 :ORA-01157 ORA-01110
2018-12-05 MySQL 批量写入
< 2025年3月 >
23 24 25 26 27 28 1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 31 1 2 3 4 5

点击右上角即可分享
微信分享提示