Acting on dropped/timed-out connections

From: "Milen A(dot) Radev" <mradev(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Acting on dropped/timed-out connections
Date: 2005-09-08 08:31:25
Message-ID: 32c009ea050908013163d6a2c2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi list!

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".

At first I thought about attaching a trigger to pg_stat_activity
table, so on delete I could take action. The only problem was it is
not a table.

Any ideas?

--
Milen A. Radev

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Wolfgang Keller 2005-09-08 09:58:43 EMS PostgreSQL Manager vs. TheKompany DataArchitect
Previous Message Richard Huxton 2005-09-08 07:11:44 Re: Cost based SELECT/UPDATE