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 786309FA634 for ; Fri, 23 Jun 2006 09:32:29 -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 01611-08 for ; Fri, 23 Jun 2006 09:32:19 -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 90AB69FA182 for ; Fri, 23 Jun 2006 09:32:19 -0300 (ADT) Received: from kingfisher.intern.logix-tt.com (Tb02f.t.pppool.de [89.55.176.47]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.logix-tt.com (Postfix) with ESMTP id F003065876 for ; Fri, 23 Jun 2006 14:33:52 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id 485D91852EF72 for ; Fri, 23 Jun 2006 14:32:29 +0200 (CEST) Message-ID: <449BDF5D.3060109@logix-tt.com> Date: Fri, 23 Jun 2006 14:32:29 +0200 From: Markus Schaber Organization: Logical Tracking and Tracing International AG, Switzerland User-Agent: Thunderbird 1.5.0.2 (X11/20060516) MIME-Version: 1.0 To: postgres performance list Subject: Re: Help tuning autovacuum - seeing lots of relationbloat References: <200606211052.43227.jody.brownell@q1labs.com> <1150898912.3309.23.camel@coppola.muc.ecircle.de> <200606211227.06618.jody.brownell@q1labs.com> <1150904541.3309.38.camel@coppola.muc.ecircle.de> In-Reply-To: <1150904541.3309.38.camel@coppola.muc.ecircle.de> 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-Archive-Number: 200606/462 X-Sequence-Number: 19819 Hi, Csaba, Csaba Nagy wrote: > Well, your application might be completely well behaved and still your > DBA (or your favorite DB access tool for that matter) can leave open > transactions in an interactive session. It never hurts to check if you > actually have "idle in transaction" sessions. It happened a few times to > us, some of those were bad coding on ad-hoc tools written by us, others > were badly behaved DB access tools opening a transaction immediately > after connect and after each successful command, effectively leaving an > open transaction when leaving it open while having lunch... Some older JDBC driver versions had the bug that they always had an open transaction, thus an application server having some pooled connections lingering around could block vacuum forever. 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