[ZBX-16987] Recovery lag arise for master Postgres database after unclean shutdown restart Created: 2019 Nov 26  Updated: 2024 Apr 10  Resolved: 2024 Mar 08

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 4.4.0, 4.4.3
Fix Version/s: None

Type: Patch request Priority: Trivial
Reporter: Sergey Assignee: Denis Rasikhov
Resolution: Fixed Votes: 0
Labels: Template_DB_PostgreSQL
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File pgsql.replication.lag.sql    
Team: Team INT

 Description   

Steps to reproduce:

  1. Create Postgresql master-slave replication servers
  2. Monitor it using standart Template DB PostgreSQL
  3. Start some workload (pgbench)
  4. Kill some process of master postgresql server with kill -9 <pid>

Result:
Restart master postgresql server
Look at pgsql.replication.lag.sec item - the values start to rise.

Expected:
When postgres start after unclean shutdown it perform some initial recovery before database became open. That recover process involves some WAL replay, so pg_last_wal_replay_lsn() points to recovery end. A lag measured by pgsql.replication.lag.sql script grows linear by time.
So i have covered original script with pg_is_in_recovery() function.

 Comments   
Comment by Edgar Akhmetshin [ 2019 Nov 29 ]

Hello Sergey,

Thank you for reporting the issue and detailed description above! Confirmed.

Regards,
Edgar

Comment by Denis Rasikhov [ 2024 Mar 08 ]

The issue has been fixed in ZBX-19897.

Generated at Wed Apr 16 17:51:32 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.