Re: Detecting backend failures via libpq / DBD::Pg - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: Detecting backend failures via libpq / DBD::Pg
Date
Msg-id ce7e8bc38b4418a17a24f8188bd7e876@biglumber.com
Whole thread Raw
In response to Re: Detecting backend failures via libpq / DBD::Pg  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


Andrew Gierth asked:
>> this is to send a simple SELECT via PQexec
>
> Why not PQexec(conn, "") ?

Because I want to leave a good clue for debugging; so 
DBAs are better able to figure out where a mystery slew of 
queries is coming from. The query is: SELECT 'DBD::Pg ping test'

Which also means the inverse is true: simple blank queries 
are guaranteed to *not* be coming from DBD::Pg.


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

iEYEAREDAAYFAlSix/YACgkQvJuQZxSWSsjILwCdHnkhYC1i+LJZkNUWjfTi5yG+
FHwAn007+arJIw62gIUO20+SxnzRT4ub
=9Rym
-----END PGP SIGNATURE-----





pgsql-hackers by date:

Previous
From: Alexey Vasiliev
Date:
Subject: Re[2]: [HACKERS] Patch: add recovery_timeout option to control timeout of restore_command nonzero status code
Next
From: Abhijit Menon-Sen
Date:
Subject: Re: What exactly is our CRC algorithm?