Greg Smith <[EMAIL PROTECTED]> writes: > On Thu, 3 Apr 2008, Tom Lane wrote: >> I'd much rather be spending our time and effort on understanding what >> broke for you, and fixing the code so it doesn't happen again.
> [ shit happens... ] Completely fair, but I still don't see how this particular patch would be a useful addition to the DBA's monitoring-tool arsenal. The scope seems too narrow. (And you still didn't tell me what the actual failure case was.) regards, tom lane -- Sent via pgsql-patches mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches