X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 2ACB69FA236 for ; Mon, 4 Sep 2006 05:06:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 50161-03-2 for ; Mon, 4 Sep 2006 05:06:23 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.logix-tt.com (mail.logix-tt.com [212.211.145.186]) by postgresql.org (Postfix) with ESMTP id DCA999FB5AA for ; Mon, 4 Sep 2006 04:35:21 -0300 (ADT) Received: from kingfisher.intern.logix-tt.com (80-219-241-140.dclient.hispeed.ch [80.219.241.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.logix-tt.com (Postfix) with ESMTP id 3B2DB656BE for ; Mon, 4 Sep 2006 09:37:27 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id 971CB18151EBC for ; Mon, 4 Sep 2006 09:35:13 +0200 (CEST) Message-ID: <44FBD731.10105@logix-tt.com> Date: Mon, 04 Sep 2006 09:35:13 +0200 From: Markus Schaber Organization: Logical Tracking and Tracing International AG, Switzerland User-Agent: Thunderbird 1.5.0.5 (X11/20060812) MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: database bloat,non removovable rows, slow query etc... References: <20060901123915.GT2266@sgala.com> <4027.1157121810@sss.pgh.pa.us> <20060901172829.GX2266@sgala.com> <12756.1157132120@sss.pgh.pa.us> <20060902083725.GB2266@sgala.com> In-Reply-To: <20060902083725.GB2266@sgala.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.16 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200609/17 X-Sequence-Number: 20703 Hi, Matteo, Matteo Sgalaberni wrote: > A my collegue JDBC application that stay in "idle intransaction" 24h/24h Just a little note: For most applications, this can be fixed updating the JDBC driver. Old versions had the behaviour of auto-opening a new backend transaction on commit/rollback, whereas new versions delay that until the first statement in the new transaction is sent. This won't fix applications that do a select and then sit idle for days before committing/rolling back, however. Those should be fixed or use autocommit mode. > Good to know this...but why this behaviour? it'is lovely...:) > > Tom , can you explain why?... It is because the transaction IDs are global per cluster. Markus -- Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org