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 82494D1B267 for ; Tue, 13 Jul 2004 07:31:42 -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 48248-04 for ; Tue, 13 Jul 2004 10:31:42 +0000 (GMT) Received: from cmailg1.svr.pol.co.uk (cmailg1.svr.pol.co.uk [195.92.195.171]) by svr1.postgresql.org (Postfix) with ESMTP id AA876D1B34F for ; Tue, 13 Jul 2004 07:31:31 -0300 (ADT) Received: from modem-1154.lemur.dialup.pol.co.uk ([217.135.132.130] helo=[192.168.0.100]) by cmailg1.svr.pol.co.uk with esmtp (Exim 4.14) id 1BkKZW-0001ze-3I; Tue, 13 Jul 2004 11:31:38 +0100 Subject: Re: are there ways for 'idle timeout'? From: Simon Riggs To: Konstantin Pelepelin Cc: mike@thegodshalls.com, pgsql-admin@postgresql.org In-Reply-To: <200407121326.41770.checat@pochtamt.ru> References: <1089430151.10763.17.camel@localhost.localdomain> <200407121326.41770.checat@pochtamt.ru> Content-Type: text/plain Organization: 2nd Quadrant Message-Id: <1089714696.17493.2448.camel@stromboli> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) Date: Tue, 13 Jul 2004 11:31:37 +0100 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200407/139 X-Sequence-Number: 14207 On Mon, 2004-07-12 at 10:26, Konstantin Pelepelin wrote: > The > > > 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! > > > Scanning through list I've not found any workaround. Have you looked at statement_timeout? This doesn't do exactly what you want, but is close enough. If you don't have it at your release, upgrade. > > 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... Best regards, Simon Riggs