From: | Roman Neuhauser <neuhauser(at)sigpipe(dot)cz> |
---|---|
To: | milen(at)radev(dot)net |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Acting on dropped/timed-out connections |
Date: | 2005-09-08 11:11:55 |
Message-ID: | 20050908111155.GA31883@isis.sigpipe.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
# mradev(at)gmail(dot)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)
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you weren't THERE. http://bash.org/?255991
From | Date | Subject | |
---|---|---|---|
Next Message | Bohdan Linda | 2005-09-08 11:23:56 | Partial commit within the trasaction |
Previous Message | Andrey Fomichev | 2005-09-08 10:20:42 | Re: PostgreSQL and XML support |