On Thu, Jul 19, 2012 at 7:17 PM, Ali Pouya <alipouya2(at)gmail(dot)com> wrote:
> On the replica I can use the function pg_last_xact_replay_timestamp().
> But on the master I only can use pg_current_xlog_location() which does not
> return a timestamp. I do not know any function returning the timestamp.
> Is there any way to get the timestamp relative to the result of
> pg_current_xlog_location() ?
According to mine own research of this problem there are no way to get it.
What I would do to monitor the replication lag is
1. execute this on master SELECT txid_current(), that will create a
minimal wal entry
2. compare pg_last_xact_replay_timestamp() with current time on replica.
assuming that clocks are in sync on both servers of course.
a database architect, software developer at PostgreSQL-Consulting.com
Jabber: gray(dot)ru(at)gmail(dot)com Skype: gray-hemp Phone: +79160686204
In response to
pgsql-admin by date
|Next:||From: Umer Asghar||Date: 2012-07-19 16:19:39|
|Subject: Postgres Database got down|
|Previous:||From: firstname.lastname@example.org||Date: 2012-07-19 15:38:50|
|Subject: autovacuum: found orphan temp|