Files
patroni/patroni
Alexander KukushkinandGitHub ce79152088 Take advantage of written_lsn and latest_end_lsn from pg_stat_wal_receiver (#3268)
The first one if available starting from PostgreSQL v13 and contains the
real write LSN. We will prefer it over value returned by
pg_last_wal_receive_lsn(), which is in fact flush LSN.

The second one is available starting from PostgreSQL v9.6 and  points to
WAL flush on the source host. In case of primary it will allow to better
calculate the replay lag, because values stored in DCS are updated only
every loop_wait seconds.
2025-02-17 15:06:36 +01:00
..
2024-04-04 17:51:26 +02:00
2024-11-12 10:06:53 +01:00
2024-10-18 09:24:51 +02:00
2024-08-13 08:51:01 +02:00
2024-12-10 14:57:47 +01:00
2024-10-18 09:24:51 +02:00
2024-11-22 14:29:59 +01:00