Skip site navigation (1) Skip section navigation (2)

Re: PQping command line tool

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PQping command line tool
Date: 2012-10-04 16:34:08
Message-ID: 2f40e7a9d6702c216ae3cd824bc96c56@biglumber.com (view raw or flat)
Thread:
Lists: pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> I was wondering recently if there was any command line tool that
> utilized PQping() or PQpingParams(). I searched the code and couldn't
> find anything and was wondering if there was any interest to have
> something like this included? I wrote something for my purposes of
> performing a health check that also supports nagios style status
> output. It's probably convenient for scripting purposes as well.

I'm not sure how useful this information would be. Most health 
checks (Nagios or otherwise) really only care if things are 
working all the up to point A or not, where point A is usually 
a simple query such as "SELECT 1". Knowing various failure states 
as returned by PQping* does not seem to fit into such tools - 
any failure needs to be handled manually.

- -- 
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201210041146
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAlBtukQACgkQvJuQZxSWSsiCbACePHFhTefoQnLwVuvIONH0JcSD
jq8AoIPusD88fX1rBcse5IreaADH7wkZ
=IRgc
-----END PGP SIGNATURE-----




In response to

Responses

pgsql-hackers by date

Next:From: Jaime CasanovaDate: 2012-10-04 16:48:42
Subject: Re: Make CREATE AGGREGATE check validity of initcond value?
Previous:From: Heikki LinnakangasDate: 2012-10-04 16:23:06
Subject: Re: Sharing more infrastructure between walsenders and regular backends (was Re: Switching timeline over streaming replication)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group