Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id DEAE99FB3A3 for ; Fri, 6 Oct 2006 07:39:57 -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 38404-09 for ; Fri, 6 Oct 2006 10:39:51 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mmp1.nems.noaa.gov (mmp1.nems.noaa.gov [140.90.121.156]) by postgresql.org (Postfix) with ESMTP id 573DE9FB39F for ; Fri, 6 Oct 2006 07:39:51 -0300 (ADT) Received: from [192.168.2.4] (ip68-227-201-228.dc.dc.cox.net [68.227.201.228]) by mmp1.nems.noaa.gov (iPlanet Messaging Server 5.2 HotFix 2.01 (built Aug 26 2004)) with ESMTPSA id <0J6P00AHFMYDZ0@mmp1.nems.noaa.gov> for pgsql-admin@postgresql.org; Fri, 06 Oct 2006 06:39:50 -0400 (EDT) Date: Fri, 06 Oct 2006 06:39:40 -0400 From: Kevin Johnson Subject: Re: Disk space consumed by pk not returned after vacuum or In-reply-to: To: Jim Nasby Cc: Bruno Wolff III , pgsql-admin@postgresql.org, Sean Webb Message-id: <4526326C.2000009@noaa.gov> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_MIN/6XN8ThxE3ec0zodQQg)" User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) References: <45080D4C.2020709@noaa.gov> <20060922170557.GB571@wolff.to> <452531AB.2050709@noaa.gov> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.589 tagged_above=0 required=5 tests=HTML_30_40, HTML_MESSAGE, HTML_TITLE_EMPTY X-Spam-Level: X-Archive-Number: 200610/41 X-Sequence-Number: 23344 This is a multi-part message in MIME format. --Boundary_(ID_MIN/6XN8ThxE3ec0zodQQg) Content-type: multipart/alternative; boundary="Boundary_(ID_Hyr6W926Ab/8lD/wXPAHOA)" --Boundary_(ID_Hyr6W926Ab/8lD/wXPAHOA) Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT You are correct, it is 7.4 we are running on a RHEL3 system. The database itself is vacuumed via cron 6 times a day. Jim Nasby wrote: > I didn't see you mention what version you're running; index bloat > shouldn't be a big issue in 7.4 and above. You also didn't mention how > often you're vacuuming the table. If you don't vacuum the table > frequently enough, you're going to get bloat, plain and simple. > > On Oct 5, 2006, at 11:24 AM, Kevin Johnson wrote: >> Thank you for the suggestion, Bruno. The clustering did the trick in >> reducing the current disk usage, however eventually the disk space >> get consumed once more. I fear that we may just need to update the >> version of Postgres to help alleviate index bloat! >> >> Bruno Wolff III wrote: >>> 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. > -- > Jim Nasby jim@nasby.net > EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) > > > -- > Jim Nasby jimn@enterprisedb.com > EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) > > -- Kevin Johnson Raytheon AWIPS Sr. Systems Engineer NWS Network Control Facility p: 301.713.9362x325 f: 301.713.1905 --Boundary_(ID_Hyr6W926Ab/8lD/wXPAHOA) Content-type: text/html; charset=ISO-8859-1 Content-transfer-encoding: 7BIT You are correct, it is 7.4 we are running on a RHEL3 system.
The database itself is vacuumed via cron 6 times a day. 

Jim Nasby wrote:
I didn't see you mention what version you're running; index bloat shouldn't be a big issue in 7.4 and above. You also didn't mention how often you're vacuuming the table. If you don't vacuum the table frequently enough, you're going to get bloat, plain and simple.

On Oct 5, 2006, at 11:24 AM, Kevin Johnson wrote:
Thank you for the suggestion, Bruno.  The clustering did the trick in reducing the current disk usage, however eventually the disk space get consumed once more.  I fear that we may just need to update the version of Postgres to help alleviate index bloat!

Bruno Wolff III wrote:
On Wed, Sep 13, 2006 at 09:53:16 -0400, Kevin Johnson <Kevin.Johnson@noaa.gov> 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.
--
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)


--
Jim Nasby                                    jimn@enterprisedb.com
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)



-- 
Kevin Johnson
Raytheon
AWIPS Sr. Systems Engineer
NWS Network Control Facility
p: 301.713.9362x325
f: 301.713.1905
--Boundary_(ID_Hyr6W926Ab/8lD/wXPAHOA)-- --Boundary_(ID_MIN/6XN8ThxE3ec0zodQQg) Content-type: text/x-vcard; charset=utf-8; name=Kevin.Johnson.vcf Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=Kevin.Johnson.vcf begin:vcard fn:Kevin Johnson n:Johnson;Kevin org:Raytheon AWIPS Team adr:SMCC II;;;1325 East West Highway;Silver Spring;MD;20910 email;internet:Kevin.Johnson@noaa.gov title:Sr. Systems Engineer tel;work:301.713.9362 x325 tel;cell:301.787.0648 x-mozilla-html:TRUE version:2.1 end:vcard --Boundary_(ID_MIN/6XN8ThxE3ec0zodQQg)--