Search Postgresql Archives

Acting on dropped/timed-out connections

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux