Re: [GENERAL] pg_last_xact_replay_timestamp() sometimes reports unlikely, very large delays

- Original Message - > > On Mar 22, 2017, at 8:06 PM, Toby Corkindale > > wrote: > > > > My best guess for what is going on is: > > - There has been no activity for hours or days, and so the oldest replayed > > transaction on the slave is genuinely

Re: [GENERAL] pg_last_xact_replay_timestamp() sometimes reports unlikely, very large delays

> On Mar 22, 2017, at 8:06 PM, Toby Corkindale > wrote: > > My best guess for what is going on is: > - There has been no activity for hours or days, and so the oldest replayed > transaction on the slave is genuinely quite old. > - Something has happened

[GENERAL] pg_last_xact_replay_timestamp() sometimes reports unlikely, very large delays

Hi all, I wondered if any experts can help me out? I currently monitor Postgresql's replication status by looking at two metrics. First I check to see if the current slave xlog replay is equal to the master -- if so, it's up to date. If it's not equal, then I look at