On 11/20/2013 01:55 AM, Fujii Masao wrote: > Yeah, I agree that we should make the logic of pg_isready more future-proof > in 9.4dev. One idea is to expose internal_ping() as a libpq function. Then, > instead of just calling PQpingParams(), we can do PQconnectStartParams(), > libpq-function-version-of-internal_ping(), PQhost(), PQport(), and PQfinish(). > That is, we get to know the host and port information by calling > PQhost() and PQport(), > after trying to connect to the server.
+1 This would allow writers of client drivers to implement their own pg_ping() functions instead of needing to go through the shell (as I currently do with pg_isready). -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
