Re: AW: AW: AW: Replication Testing- How to introduce a Lag - Mailing list pgsql-novice

From Laurenz Albe
Subject Re: AW: AW: AW: Replication Testing- How to introduce a Lag
Date
Msg-id 0e00fcc0062b59b88f98dba4900ce49d5a9a3fea.camel@cybertec.at
Whole thread Raw
In response to AW: AW: AW: Replication Testing- How to introduce a Lag  ("Subramanian,Ramachandran" <ramachandran.subramanian@alte-leipziger.de>)
Responses AW: AW: AW: AW: Replication Testing- How to introduce a Lag
List pgsql-novice
On Mon, 2026-03-23 at 05:55 +0000, Subramanian,Ramachandran wrote:
> Thank you so much for your guidance,  Today morning I noticed the columns being null . 
>
> > streaming | 0/491179E8 | 0/491179E8 | 0/491179E8 | 0/491179E8 |           |           |            |
>
> Does it make sense to use the below SQL as a primary health check ?
>
> [postgres@Source_server~]$ psql -p 5432 -c " select  pg_wal_lsn_diff(sent_lsn,replay_lsn) from pg_stat_replication"
>  pg_wal_lsn_diff
> -----------------
>                0
> (1 row)

No; you want to measure the lag between the primary's current WAL position and
what was already replayed on the standby:

  SELECT pg_wal_lsn_diff(pg_current_wal_lsn(), replay_lsn)
  FROM pg_stat_replication;

Yours,
Laurenz Albe



pgsql-novice by date:

Previous
From: hubert depesz lubaczewski
Date:
Subject: Re: Old software
Next
From: "Subramanian,Ramachandran"
Date:
Subject: AW: AW: AW: AW: Replication Testing- How to introduce a Lag