Re: Prepared transactions vs novice DBAs, again

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

> The pgsql-admin list has just seen another instance where careless use
> of prepared transactions brought down a database, and the DBA (who had
> no idea what a prepared transaction even was) had no idea how to fix it.

Just as a followup (and I already posted this on the pgsql-admin thread),
the check_postgres script now has a specific check for this very case.
It simply checks the age of entries in pg_prepared_xacts and gives
a warning if the number is at or over the given threshhold (defaults
to 1 second). I'm still a heavy +1 on making the default Postgres
configuration value 0, but hopefully this will help.

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

iEYEAREDAAYFAkoAW0wACgkQvJuQZxSWSsgGRgCePjErqeAPEv4MLJzgEnh/tXtA
yLEAoPhBNvaWvcmTF9D8faZzI044zpBL
=ouXW
-----END PGP SIGNATURE-----