Skip site navigation (1) Skip section navigation (2)

Re: Server unreliability

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-advocacy(at)postgresql(dot)org
Subject: Re: Server unreliability
Date: 2004-09-29 23:51:08
Message-ID: cf9457bfb5e13085fdc56c90f09c13ea@biglumber.com (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-www
-----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(at)turnstep(dot)com
PGP Key: 0x14964AC8 200409291947
 
-----BEGIN PGP SIGNATURE-----
 



In response to

Responses

pgsql-www by date

Next:From: Marc G. FournierDate: 2004-09-29 23:56:11
Subject: Re: Server unreliability
Previous:From: Marc G. FournierDate: 2004-09-29 23:35:51
Subject: Re: [pgsql-advocacy] Server unreliability

pgsql-advocacy by date

Next:From: Marc G. FournierDate: 2004-09-29 23:56:11
Subject: Re: Server unreliability
Previous:From: Marc G. FournierDate: 2004-09-29 23:35:51
Subject: Re: [pgsql-advocacy] Server unreliability

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group