Peter Eisentraut <[EMAIL PROTECTED]> writes: > The problem, as I understand it, is that if you have a long-running > query and the client process disappears, the query keeps running and > holds whatever resources it may have until it finishes.
There is a trivial solution for this: it's called statement_timeout. If the concern is that a process may block other processes for a long time, what does it matter whether the client is still connected or not? It's the long-running command in itself that is the problem. So you limit the time the command can run. It might be interesting to think about a transaction_timeout as well, to bound the time locks can be held. But none of this has anything to do with "high availability" as I understand the term. It looks more like a forcing function to make your users fix poorly-written client software ;-) regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org