[ClusterLabs] PAF fails to promote slave: Can not get current node LSN location

Jehan-Guillaume de Rorthais jgdr at dalibo.com
Wed Jul 10 11:15:59 EDT 2019

On Wed, 10 Jul 2019 17:08:45 +0200
Tiemen Ruiten <t.ruiten at tech-lab.io> wrote:

> On Wed, Jul 10, 2019 at 2:47 PM Jehan-Guillaume de Rorthais <jgdr at dalibo.com>
> wrote:
> > >
> > > I double-checked monitoring data: there was approximately one minute of
> > > replication lag on one slave and two minutes of replication lag on the
> > > other slave when the original issue occurred.  
> >
> > what lag? current primary LSN versus sent, received, synced or replayed?
> >  
> Replay, I use pg_last_xact_replay_timestamp to monitor lag.

The "receive" one might show a very different lag, more representative of
a bottleneck between both node. Especially if you have some read activity on
the standby.

Compare with values in pg_stat_replication on primary side.

More information about the Users mailing list