| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Phil Sorber <phil(at)omniti(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PQping command line tool |
| Date: | 2012-10-03 15:41:19 |
| Message-ID: | 5874.1349278879@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> I don't see any tool using PQping except pg_ctl. Perhaps we should
> modify "pg_ctl status" to use PQping. Right now is only checks the
> postmaster.pid file, and checks to see that the pid is a running
> postmaster. What it currently doesn't do is to check if the server is
> accepting connections with PQping(), like we do for "pg_ctl -w start".
The thing about pg_ctl is that it requires access to the data directory
(and still would, in the variant you propose). If we were going to do
something like what Phil suggests then I think it ought to be something
usable remotely.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2012-10-03 15:42:44 | Re: PQping command line tool |
| Previous Message | Phil Sorber | 2012-10-03 15:40:30 | Re: PQping command line tool |