Re: [ADMIN] are there ways for 'idle timeout'?

[Konstantin Pelepelin]

On Tue, 13 Jul 2004 11:31:37 +0100, Simon Riggs <[EMAIL PROTECTED]>  
wrote:

> > best solution I see is having an (per session)
> > idle_transaction_timeout or idle_connection_timeout
> > setting. But there is no such thing in postgres!

Have you looked at statement_timeout?
This doesn't do exactly what you want, but is close enough.
'statement_timeout' will abort statements locked by "locking idle  
transaction", but I need to abort "locking idle transaction" itself.


> Looking into TODO I don't see any plans for it.
> > Is it too difficult implementing or I've missed
> > something or are there workarounds?
This might be something you could do...
If I'd know C and Postgres internals.
(Then there is no assurance that developers will say "Yes, it's good". And  
I'm not sure it is easy.)

For now, I need to create some additional monitoring tool and inegrate it  
with all our applications.

*Very disappointed*
Konstantin
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
     subscribe-nomail command to [EMAIL PROTECTED] so that your
     message can get through to the mailing list cleanly