X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 672D5D1B1D0 for ; Tue, 13 Jul 2004 14:29:53 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 59549-05 for ; Tue, 13 Jul 2004 17:29:45 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 88112D1B1C7 for ; Tue, 13 Jul 2004 14:29:44 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i6DHThi7006131 for ; Tue, 13 Jul 2004 17:29:43 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i6DHNn5n005067 for pgsql-admin@postgresql.org; Tue, 13 Jul 2004 17:23:49 GMT From: "Konstantin Pelepelin" X-Newsgroups: comp.databases.postgresql.admin Subject: Re: are there ways for 'idle timeout'? Date: Tue, 13 Jul 2004 21:24:21 +0400 Organization: DTF Lines: 27 Message-ID: References: <1089430151.10763.17.camel@localhost.localdomain> <200407121326.41770.checat@pochtamt.ru> <1089714696.17493.2448.camel@stromboli> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; delsp=yes; charset=koi8-r Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@news.hub.org User-Agent: Opera M2/7.51 (Linux, build 689) To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.4 tagged_above=0.0 required=5.0 tests=DNS_FROM_RFCI_DSN X-Spam-Level: * X-Archive-Number: 200407/151 X-Sequence-Number: 14219 On Tue, 13 Jul 2004 11:31:37 +0100, Simon Riggs 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