X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 55F2F9FB5C4 for ; Fri, 22 Sep 2006 14:23:08 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 43154-05-2 for ; Fri, 22 Sep 2006 17:21:11 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from wolff.to (wolff.to [66.93.197.194]) by postgresql.org (Postfix) with SMTP id B05F79FB4A0 for ; Fri, 22 Sep 2006 13:56:19 -0300 (ADT) Received: (qmail 2963 invoked by uid 500); 22 Sep 2006 17:05:58 -0000 Date: Fri, 22 Sep 2006 12:05:57 -0500 From: Bruno Wolff III To: Kevin Johnson Cc: pgsql-admin@postgresql.org, Sean Webb Subject: Re: Disk space consumed by pk not returned after vacuum or reindex Message-ID: <20060922170557.GB571@wolff.to> Mail-Followup-To: Bruno Wolff III , Kevin Johnson , pgsql-admin@postgresql.org, Sean Webb References: <45080D4C.2020709@noaa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45080D4C.2020709@noaa.gov> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200609/246 X-Sequence-Number: 23160 On Wed, Sep 13, 2006 at 09:53:16 -0400, Kevin Johnson wrote: > > We have a database, which consistently consumes more and more of the > disk space in it's lvol until it reaches 100%. So far, we have tried to > run a full vacuum on the database, with limited success. Eventually, we > had to drop and reload the database with the same data inside. It > brought the disk usage down to 73%. It then began to creep once more > toward 100%. After some research, I was able to use the pg_class > catalog to find that the items which are expanding the quickest are > primary key (btree) indexes. I attempted to run a REINDEX on one of the > tables with the pk taking up the largest amount of space. The usage > according to pg_class dropped dramatically, however the disk space was > not returned to the system. So I attempted another full vacuum > afterwards, and still nothing was returned to the system. These tables > are updated extremely frequently (although their total number of rows is > close to constant), which is my guess as to why the pk indexes increase > so rapidly in terms of their disk usage. Unfortunately, PostgreSQL > knowledge is limited, and I was wondering if anyone had experienced > something similar / knows what else we can do to return this disk space > back to the system? This is possibly index bloat due to new keys always being larger than existing keys. This was fixed in later releases. There is still some potential for bloat due to fragmentation, but I believe that has a constant bound. You might try using the cluster command. I think that will both clean up the indexes and remove dead rows and do it faster than using a vacuum full and reindexing. The downside is that the table will be unavailable during the cluster which might be a deal breaker for you.