Обсуждение: Monitor repl slot size
location -> lsnHello,we used to monitor the replication slot size on postgres 9.6.6 with the following query:SELECT pg_xlog_location_diff(pg_current_xlog_location(), restart_lsn) FROM pg_replication_slots WHERE slot_name = 'SLOT NAME';We are moving to postgres 10.4 and we saw the pg_xlog_location_diff is not there anymore.
xlog -> wal
SELECT pg_wal_lsn_diff(pg_current_wal_insert_lsn(), restart_lsn) FROM pg_replication_slots;
I know we can re-create it following this link : https://github.com/DataDog/integrations-core/issues/907but, is there any better way to do it? Any replacement for that function on postgres 10?Thanks a lot,Nicola
-- Achilleas Mantzios IT DEV Lead IT DEPT Dynacom Tankers Mgmt
From: Nicola Contu [mailto:nicola.contu@gmail.com]
Sent: Friday, July 13, 2018 6:19 AM
To: pgsql-general@lists.postgresql.org
Cc: Alessandro Aste <Alessandro.aste@gtt.net>
Subject: Monitor repl slot size
Hello,
we used to monitor the replication slot size on postgres 9.6.6 with the following query:
SELECT pg_xlog_location_diff(pg_current_xlog_location(), restart_lsn) FROM pg_replication_slots WHERE slot_name = 'SLOT NAME';
We are moving to postgres 10.4 and we saw the pg_xlog_location_diff is not there anymore.
I know we can re-create it following this link : https://github.com/DataDog/integrations-core/issues/907
but, is there any better way to do it? Any replacement for that function on postgres 10?
Thanks a lot,
Nicola
I’m compare current_wal_lsn to confirmed_flush_lsn:
SELECT confirmed_flush_lsn, pg_current_wal_lsn(), (pg_current_wal_lsn() - confirmed_flush_lsn) AS lsn_distance -- returned as NUMERIC
FROM pg_catalog.pg_replication_slots
WHERE slot_name = 'Slot NAME';
Regards,
Igor Neyman