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

Re: [pgsql-advocacy] Server unreliability

From: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
To: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
Cc: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>,Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-advocacy(at)postgresql(dot)org,Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,PostgreSQL www <pgsql-www(at)postgresql(dot)org>
Subject: Re: [pgsql-advocacy] Server unreliability
Date: 2004-09-29 23:24:31
Message-ID: 20040929202326.Q3407@ganymede.hub.org (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-www
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(at)hub(dot)org           Yahoo!: yscrappy              ICQ: 7615664

In response to

Responses

pgsql-www by date

Next:From: Marc G. FournierDate: 2004-09-29 23:35:51
Subject: Re: [pgsql-advocacy] Server unreliability
Previous:From: Josh BerkusDate: 2004-09-29 23:13:20
Subject: Re: Server unreliability

pgsql-advocacy by date

Next:From: Marc G. FournierDate: 2004-09-29 23:35:51
Subject: Re: [pgsql-advocacy] Server unreliability
Previous:From: Josh BerkusDate: 2004-09-29 23:13:20
Subject: Re: Server unreliability

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