X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id EC2C132A0D7;
	Thu, 30 Sep 2004 00:25:07 +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 42805-07; Wed, 29 Sep 2004 23:24:53 +0000 (GMT)
Received: from hub.org (hub.org [200.46.204.220])
	by svr1.postgresql.org (Postfix) with ESMTP id C9A94329D5F;
	Thu, 30 Sep 2004 00:24:47 +0100 (BST)
Received: from localhost (unknown [200.46.204.144])
	by hub.org (Postfix) with ESMTP id 92CF8490A19;
	Wed, 29 Sep 2004 20:24:44 -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 41151-10; Wed, 29 Sep 2004 23:24:30 +0000 (GMT)
Received: from ganymede.hub.org (blk-222-46-91.eastlink.ca [24.222.46.91])
	by hub.org (Postfix) with ESMTP id 6FC63490A1E;
	Wed, 29 Sep 2004 20:24:29 -0300 (ADT)
Received: by ganymede.hub.org (Postfix, from userid 1000)
	id B1B0534493; Wed, 29 Sep 2004 20:24:31 -0300 (ADT)
Received: from localhost (localhost [127.0.0.1])
	by ganymede.hub.org (Postfix) with ESMTP id AC9ED33C20;
	Wed, 29 Sep 2004 20:24:31 -0300 (ADT)
Date: Wed, 29 Sep 2004 20:24:31 -0300 (ADT)
From: "Marc G. Fournier" <scrappy@postgresql.org>
X-X-Sender: scrappy@ganymede.hub.org
To: Alvaro Herrera <alvherre@dcc.uchile.cl>
Cc: "Marc G. Fournier" <scrappy@postgresql.org>,
	Josh Berkus <josh@agliodbs.com>, pgsql-advocacy@postgresql.org,
	Bruce Momjian <pgman@candle.pha.pa.us>,
	PostgreSQL www <pgsql-www@postgresql.org>
Subject: Re: [pgsql-advocacy] Server unreliability
In-Reply-To: <20040929201556.GB5275@dcc.uchile.cl>
Message-ID: <20040929202326.Q3407@ganymede.hub.org>
References: <200409291713.i8THDLn14086@candle.pha.pa.us>
	<200409291152.05741.josh@agliodbs.com>
	<20040929155958.U93533@ganymede.hub.org>
	<20040929201556.GB5275@dcc.uchile.cl>
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/236
X-Sequence-Number: 5306

On Wed, 29 Sep 2004, Alvaro Herrera wrote:

> about pg_query not getting a good connection or similar problems. 
> Isn't normal advice to check return codes before even trying to use the 
> connections?  Why isn't this done in the main postgresql.org code, where 
> anyone can see it, is beyond me.  Of course the solution to the 
> underlying problem is to restart the Postgres server, but why should we 
> inform the user that Postgres' own database server is down, in the worst 
> possible way?

Just curious here, but when/where?  We haven't had a database issue in 
quite awhile that *I'm* aware of ... in fact, the whole web site is 
static, generated periodically from .php files, so that the mirrors can 
pick things up properly, so there should never be a 'cannot connect to 
database' issue, since there are no connections to the database being made 
...

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664