[HACKERS] Finding slave WAL application time delay

2010-07-20 Thread Bruce Momjian
Someone at OSCON just asked if there is a way to find the _time_ delay
between received and applied WAL.  Right now
pg_last_xlog_replay_location() only reports the information in WAL
scale.  It would be nice to report that in time, e.g. milliseconds.

Because an idle master will not generate WAL, I don't think there is a
way to report the time delay in receiving WAL.

-- 
  Bruce Momjian  br...@momjian.ushttp://momjian.us
  EnterpriseDB http://enterprisedb.com

  + None of us is going to be here forever. +

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers


Re: [HACKERS] Finding slave WAL application time delay

2010-07-20 Thread Robert Haas
On Tue, Jul 20, 2010 at 3:13 PM, Bruce Momjian br...@momjian.us wrote:
 Someone at OSCON just asked if there is a way to find the _time_ delay
 between received and applied WAL.  Right now
 pg_last_xlog_replay_location() only reports the information in WAL
 scale.  It would be nice to report that in time, e.g. milliseconds.

There's probably more than one way you can define this.  See, for
example, previous discussions of max_standby_delay.

 Because an idle master will not generate WAL, I don't think there is a
 way to report the time delay in receiving WAL.

You could certainly come up with a sensible definition for this,
though there are also nonsensical ones.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers