X-Original-To: pgsql-advocacy-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6216132A0B4 for ; Thu, 30 Sep 2004 01:10:20 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 52975-10 for ; Thu, 30 Sep 2004 00:10:17 +0000 (GMT) Received: from hub.org (hub.org [200.46.204.220]) by svr1.postgresql.org (Postfix) with ESMTP id F38E032A068 for ; Thu, 30 Sep 2004 01:10:16 +0100 (BST) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id 439BC490A2E for ; Wed, 29 Sep 2004 21:10:13 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 52975-09; Thu, 30 Sep 2004 00:09:59 +0000 (GMT) Received: from ganymede.hub.org (blk-222-46-91.eastlink.ca [24.222.46.91]) by hub.org (Postfix) with ESMTP id E00EA490A34; Wed, 29 Sep 2004 21:09:58 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 2B79F33C20; Wed, 29 Sep 2004 21:10:02 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 27DD133C16; Wed, 29 Sep 2004 21:10:02 -0300 (ADT) Date: Wed, 29 Sep 2004 21:10:02 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Greg Sabino Mullane Cc: pgsql-advocacy@postgresql.org Subject: Re: Server unreliability In-Reply-To: Message-ID: <20040929210735.M3407@ganymede.hub.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200409/221 X-Sequence-Number: 5464 On Wed, 29 Sep 2004, Greg Sabino Mullane wrote: > > -----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 fault, sorry ... I've been going through and cleaning up the code, removed the right banner ad, and missed an include directory :( > 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. In your case, you caught it between edits ... again, sorry about that ... the main web site itself is tested on a beta site first, so if you ever see an error there, its definitely not from lack of testing by the -www crew ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664