Juan José Ivars Poquet

I tried it but i get that error: `# Fuse_util.c:53:10: fatal error: 'sys/xattr.h' file not found`

I can confirm that it works with cmount compilation option: ``` pkg install gmake git clone https://github.com/rclone/rclone.git cd rclone/ gmake GOTAGS=cmount /root/go/bin/rclone cmount gdrive: /mnt/gdrive --allow-other --config /root/.config/rclone/rclone.conf ``` ```...

+1 for FreeBSD

`Are there recommended metrics/alerts for monitoring replication? Server-side? Client-side?` If you want to monitor lag looking at the Primary server I think it would be better to monitor [replay_lag](https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-REPLICATION-VIEW) but...

@IamLuksha This method does not work in postgresql>=10 or postgresql

@IamLuksha Correct me if I am wrong. It can be two kind of lag: - Local-Secondary server lag, the information was received by the Secondary server and written to disk...

When you say: `In your case you need to check the connection between the servers` Check the connection using node_exporter or any other external monitoring system? Or querying some PosqtgreSQL...

Hello @IamLuksha , what do you think about monitoring lag and availability from Primary server? You can detect broken synchronizations, if you know It's IP/FQDN: `SELECT COUNT(*) FROM pg_stat_replication WHERE...

This affects replication monitoring in the way that if only pg_up and pg_replication_lag_seconds are monitored in Secondary servers and there's a network outage between Primary and Secondary servers, Secondary servers...