Re: Acting on dropped/timed-out connections - Mailing list pgsql-general

From Milen A. Radev
Subject Re: Acting on dropped/timed-out connections
Date
Msg-id 32c009ea050908042963fbe3f7@mail.gmail.com
Whole thread Raw
In response to Re: Acting on dropped/timed-out connections  (Roman Neuhauser <neuhauser@sigpipe.cz>)
List pgsql-general
On 08/09/05, Roman Neuhauser <neuhauser@sigpipe.cz> wrote:
> # mradev@gmail.com / 2005-09-08 11:31:25 +0300:
> > We have a daemon programme that acts as a pgsql client. It writes in a
> > DB the status of its own clients. And we have a different daemon that
> > needs to read that status information and decide upon it. The problem
> > is that the first daemon is a little fragile and from time to time it
> > crashes. I need to be able to monitor its connection to the PgSQL and
> > if it drops (times-out) to mark the status of all of its clients as
> > "unavailable" or "unknown".
>
>     Do you prefer knowing that the daemon failed, or having it
>     automaticly restarted the very same moment it crashes? If the
>     latter, take a look at djb's daemontools, or one of its open source
>     lookalikes (http://smarden.org/runit/,
>     http://offog.org/code/freedt.html).
>

It's the former - in this case I'm not responsible (read "I don't
care") about the daemon. I care about the (reasonable) veracity of the
data in the DB.


--
Milen A. Radev

pgsql-general by date:

Previous
From: Roman Neuhauser
Date:
Subject: Re: Acting on dropped/timed-out connections
Next
From: Karsten Hilbert
Date:
Subject: Re: How to write jobs in postgresql