On Tue, Jan 12, 2010 at 4:22 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > It would be more straightforward to have a function in the standby to > return the current replay location. It feels more logical to poll the > standby to get the status of the standby, instead of indirectly from the > master. Besides, the master won't know how far the standby is if the > connection to the standby is broken. > > Maybe we should just change the existing pg_current_xlog_location() > function to return that when recovery is in progress. It currently > throws an error during hot standby.
Sounds good. I'd like to hear from someone which location should be returned by that function (WAL receive/write/flush/replay location?). I vote for WAL flush location because it's important for me to know how far the standby can replay the WAL, i.e., how much transactions might be lost at failover. And, it's also OK to provide the dedicated function for WAL replay location. Thought? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
