However I'm not sure that pg_stat_replication currently has the
necessary information on either side to measure the lag (in time
transactions, but how do I know when a transaction was committed? or
number of transactions?).
The BDR codebase now has a handy function to report when a transaction
was committed, pg_get_transaction_committime(xid) .
This looks handy for monitoring a replication setup.
It should really be in core...
Any plans? Or is there other ways to get this kind of information in core?
--
Fabien.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
