public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alvaro Herrera <[email protected]>
To: Marc G. Fournier <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: [email protected]
Cc: Bruce Momjian <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: [pgsql-advocacy] Server unreliability
Date: Thu, 30 Sep 2004 09:26:29 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Wed, Sep 29, 2004 at 08:24:31PM -0300, 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?

I don't remember an exact date or place, just that I've seen that happen
more than three times and I've always thought it was bad programming
practice.  It has been very annoying, mainly because it means casual
visitors could see those and possible think Postgres reliability sucked.
Perhaps it has been fixed since then.

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"The important things in the world are problems with society that we don't
understand at all. The machines will become more complicated but they won't
be more complicated than the societies that run them."    (Freeman Dyson)

view thread (74+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [pgsql-advocacy] Server unreliability
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox