Vladimir Luksha

Maybe I'm wrong There is no way to check and test right now But in versions above 9.3 pg_last_xact_replay_timestamp does not work correctly. And in the proposed commit it is...

@SuperQ > Are there recommended metrics/alerts for monitoring replication? Server side? Client side? Myabe [reply_time](https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-REPLICATION-VIEW). I need some time for test. Maybe next week. I don't have a working cluster...

> Anyway, with the current Secondary metric monitoring, we can monitor lag if we apply the proposed patch, there are two queries, one for PostgreSQL>=10 and another for PostgreSQL

> @IamLuksha This method does not work in postgresql>=10 or postgresql 9.3. But you propose to use it for

> Have I understood the whole problem correctly? Yes! So we need to check `pg_last_wal_receive_lsn () = pg_last_wal_replay_lsn ()`

> Check the connection using node_exporter or any other external monitoring system? Or querying some PosqtgreSQL data? Every method can be used I don't remember if Postgres has a method...