| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Phil Sorber <phil(at)omniti(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [WIP] pg_ping utility |
| Date: | 2012-11-26 18:14:52 |
| Message-ID: | 20121126181452.GB23214@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 26, 2012 at 10:26:27AM -0500, Peter Eisentraut wrote:
> On 11/23/12 9:48 AM, Michael Paquier wrote:
> > We waited a couple of days for feedback for this feature. So based on
> > all the comments provided by everybody on this thread, perhaps we should
> > move on and implement the options that would make pg_ping a better
> > wrapper for PQPing. Comments?
>
> Personally, I still don't see the general utility of this. For
> monitoring, psql -c 'select 1' is much more useful. For network
> analysis, you can use network analysis tools. The niche for pg_ping in
> between those is so narrow that I cannot see it.
I would normally agree with this analysis, but pg_ctl -w certainly need
this ping functionality, so it kind of makes sense that others might
need it too.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-11-26 18:23:24 | Re: Upcoming back-branch releases |
| Previous Message | Robert Haas | 2012-11-26 18:06:56 | Re: Suggestion for --truncate-tables to pg_restore |