public inbox for [email protected]  

help / color / mirror / Atom feed

From: Marc G. Fournier <[email protected]>
To: Gavin Sherry <[email protected]>
Cc: Chris Ryan <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: [pgsql-advocacy] Server unreliability
Date: Sat, 2 Oct 2004 17:08:40 -0300 (ADT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>


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: [email protected]           Yahoo!: yscrappy              ICQ: 7615664

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]
  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