Re: Server unreliability - Mailing list pgsql-advocacy

From Greg Sabino Mullane
Subject Re: Server unreliability
Date
Msg-id cf9457bfb5e13085fdc56c90f09c13ea@biglumber.com
Whole thread Raw
In response to Re: [pgsql-www] Server unreliability  ("Marc G. Fournier" <scrappy@postgresql.org>)
Responses Re: Server unreliability  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-advocacy
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> Just curious here, but when/where?  We haven't had a database issue in
> quite awhile that *I'm* aware of

Earlier this very day I got a page full of php erros when I tried
to view one of the mailing list "by thread". I would have wrote down
the errors and reported it. but it seems so par for the course I
did not bother.

My other concern is that often myself or someone else points out these
errors on the list, and *then* they are fixed. They should be caught
before this, either by testing by the people who make the changes
(which I've seen fail to happen), or by some sort of automated script
that does some quick basic checks.

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200409291947

-----BEGIN PGP SIGNATURE-----




pgsql-advocacy by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: [pgsql-www] Server unreliability
Next
From: Mark Harrison
Date:
Subject: Re: Server unreliability