From: | yhe <yinghe0101(at)yahoo(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | strem replication standby lag check |
Date: | 2014-01-17 19:16:55 |
Message-ID: | 1389986215594-5787682.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
hi, all,
I know we can connect to primary and SELECT pg_current_xlog_location(); (eg.
'0/36A77900') to get primary xlog position then connect to the standby to do
the following to get the byte lag:
select pg_xlog_location_diff('0/36A77900',pg_last_xlog_replay_location());
0/36A77900 is the xlog position from primary.
My question is that is there a way I can connect to the primary on the
standby host using replica user which i already have the primary_conninfo in
the recovery.conf and get the result of SELECT pg_current_xlog_location();
of the primary so I can simply write a function on the standby to return the
lag in bytes in one call.
any way I can do that without a dblink?
Thank you if any one can help.
best,
Ying
--
View this message in context: http://postgresql.1045698.n5.nabble.com/strem-replication-standby-lag-check-tp5787682.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Murthy Nunna | 2014-01-17 22:00:35 | Postgresql v9.2.4 Kerberos Client Authentication |
Previous Message | Steve Crawford | 2014-01-17 16:42:39 | Re: Checking replication slave state |