Re: Consistently report CONNECTION_BAD state to applications.

"Greg Sabino Mullane" <greg-738XdyZ4GzZWk0Htik3J/[email protected]> Mon, 2 Sep 2013 03:39:57 -0000

Newsgroups	gmane.comp.db.postgresql.dbdpg
Message-ID	<[email protected]>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


Rainer Weikusat <[email protected]> wrote:
> Attached is a patch which (IMHO) improves this situation by introducing
> a _fatal_sqlstate function setting the sqlstate of the dbh either to
> 08000 (connection exception) or 22000 (data exception), based on the
> result of PQconnStatus.

Patch has been (finally) applied! Thank you for this.

commit 202ae11f0723f05a6b43f7a49bd70300274162e1

- -- 
Greg Sabino Mullane greg-738XdyZ4GzZWk0Htik3J/[email protected]
PGP Key: 0x14964AC8 201309012338
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAlIkCHAACgkQvJuQZxSWSsjqLQCdHDljzVvKrDXQY4bk5XEbggO+
BVcAoJwPqyzw5AU+V6hRh2Dri4Qol+Xw
=o3+t
-----END PGP SIGNATURE-----