Date: Sat, 2 Oct 2004 17:08:40 -0300 (ADT)
From: "Marc G. Fournier" <scrappy@postgresql.org>
To: Gavin Sherry <swm@linuxworld.com.au>
Cc: Chris Ryan <xgbe@yahoo.com>,
	PostgreSQL www <pgsql-www@postgresql.org>
Subject: Re: [pgsql-advocacy] Server unreliability
In-Reply-To: <Pine.LNX.4.58.0410022333110.30224@linuxworld.com.au>
Message-ID: <20041002170759.Y64687@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>
	<20040929202326.Q3407@ganymede.hub.org>
	<Pine.LNX.4.58.0410022333110.30224@linuxworld.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed


Chris?  Some extra error checking needed, maybe?


On Sat, 2 Oct 2004, Gavin Sherry wrote:

> On Wed, 29 Sep 2004, Marc G. Fournier wrote:
>
>> 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
>
> I know this isn't on the main site but:
>
> http://www.alcove.com.au/~swm/gborg.png
>
> Gavin
>

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