X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 118C1D1B508 for ; Tue, 21 Oct 2003 12:13:34 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 52043-10 for ; Tue, 21 Oct 2003 09:13:06 -0300 (ADT) Received: from pns.mm.eutelsat.org (pns.mm.eutelsat.org [194.214.173.227]) by svr1.postgresql.org (Postfix) with ESMTP id CF477D1B527 for ; Tue, 21 Oct 2003 09:13:01 -0300 (ADT) Received: from nts-03.mm.eutelsat.org (localhost [127.0.0.1]) by pns.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id h9LBFHw29703; Tue, 21 Oct 2003 13:15:17 +0200 Received: from bigfoot.com (accesspoint.mm.eutelsat.org [194.214.173.4]) by nts-03.mm.eutelsat.org (8.11.6/linuxconf) with ESMTP id h9LC4HR25098; Tue, 21 Oct 2003 14:04:18 +0200 Message-ID: <3F9522B2.2010009@bigfoot.com> Date: Tue, 21 Oct 2003 14:12:34 +0200 From: Gaetano Mendola User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "pgsql-performance@postgresql.org" Cc: Andrew Sullivan Subject: Re: index file bloating still in 7.4 ? References: <200310181458.15575.josh@agliodbs.com> <16213.1066530060@sss.pgh.pa.us> <17172.1066542509@sss.pgh.pa.us> <19692.1066578442@sss.pgh.pa.us> <15968.1066686172@sss.pgh.pa.us> <20031021105655.GB9837@libertyrms.info> In-Reply-To: <20031021105655.GB9837@libertyrms.info> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/522 X-Sequence-Number: 4270 Andrew Sullivan wrote: > On Mon, Oct 20, 2003 at 05:42:52PM -0400, Tom Lane wrote: > > >>hold of these dead rows instead of recycling them. I suspect you have >>a client process somewhere that is holding an open transaction for a >>long time ... probably not doing anything, just sitting there with an >>unclosed BEGIN ... > > > Which could be because you're doing something nasty with one of the > "autocommit=off" clients. Most of the client libraries implement > this by doing "commit;begin;" at every commit. This means you have > way more idle in transaction connections than you think. Look in > pg_stat_activity, assuming you've turned on query echoing. Or is enough do a ps -eafwww | grep post to see the state of the connections Regards Gaetano Mendola