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 B76FFD1B4E1 for ; Mon, 20 Oct 2003 21:43:28 +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 13813-08 for ; Mon, 20 Oct 2003 18:42:59 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 746ECD1B510 for ; Mon, 20 Oct 2003 18:42:56 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id h9KLgqit015969; Mon, 20 Oct 2003 17:42:52 -0400 (EDT) To: Seum-Lim Gan Cc: josh@agliodbs.com, pgsql-performance@postgresql.org Subject: Re: index file bloating still in 7.4 ? In-reply-to: References: <200310181458.15575.josh@agliodbs.com> <16213.1066530060@sss.pgh.pa.us> <17172.1066542509@sss.pgh.pa.us> <19692.1066578442@sss.pgh.pa.us> Comments: In-reply-to Seum-Lim Gan message dated "Sun, 19 Oct 2003 11:55:57 -0500" Date: Mon, 20 Oct 2003 17:42:52 -0400 Message-ID: <15968.1066686172@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/517 X-Sequence-Number: 4265 Seum-Lim Gan writes: > [ successive outputs from VACUUM ANALYZE ] FWIW, I don't think your problem is really index bloat at all, it's more like too-many-dead-rows bloat. Note that the number of "dead row versions" is climbing steadily from run to run: > DETAIL: 101802 dead row versions cannot be removed yet. > DETAIL: 110900 dead row versions cannot be removed yet. > DETAIL: 753064 dead row versions cannot be removed yet. > DETAIL: 765328 dead row versions cannot be removed yet. It's hardly the index's fault that it's growing, when it has to keep track of an ever-increasing number of rows. The real question is what you're doing that requires the system to keep 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 ... regards, tom lane