From: | "Konstantin Pelepelin" <checat(at)pochtamt(dot)ru> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: are there ways for 'idle timeout'? |
Date: | 2004-07-13 17:24:21 |
Message-ID: | opsa26mvrlhocrah@cathost.of.dtf.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, 13 Jul 2004 11:31:37 +0100, Simon Riggs <simon(at)2ndquadrant(dot)com>
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
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Chandler | 2004-07-13 20:01:06 | Using PL/pgSQL with statically built PostgreSQL binaries |
Previous Message | Matt Wong | 2004-07-13 16:35:01 | help with lost pghoster website |