Alvaro Herrera wrote:
Kevin Grittner wrote:
The reason is that we don't want certain other processes attempting to
start until and unless the database they use has started successfully.
This is something we're not quite ready on, yet. We need some mechanism
that allows scripts to verify not only that postmaster started, but also
that it has finished recovery. You can sort-of do it by attempting a
connection and checking the error message, but it's ugly. There was
talk about a pg_ping utility years ago, but nobody got around to writing
it ...
Can't you use pg_controldata to see whether it is in recovery or not?
Seems like you've got a way to see if it's running, seeing if it is in
recovery should therefore be pretty straightforward, no?
--
Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC 27560
919-463-0999/877-258-8987
http://www.otg-nc.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
