Re: Disk space consumed by pk not returned after vacuum or reindex

From: Jim Nasby <jimn(at)enterprisedb(dot)com>
To: Kevin Johnson <Kevin(dot)Johnson(at)noaa(dot)gov>
Cc: Bruno Wolff III <bruno(at)wolff(dot)to>, pgsql-admin(at)postgresql(dot)org, Sean Webb <Sean(dot)Webb(at)noaa(dot)gov>
Subject: Re: Disk space consumed by pk not returned after vacuum or reindex
Date: 2006-10-06 15:37:51
Message-ID: 8A3D37C4-8DA1-4ABE-A41E-A02FF03C2149@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Oct 6, 2006, at 5:39 AM, Kevin Johnson wrote:
> 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.

For a heavy update load, even 6 times a day may not be enough.

Also, remember that the size you get after a REINDEX will be
unreasonably low, because there will be very little free space in the
index. That's fine if you won't be updating the table much, but
otherwise the index will have no choice but to grow.
--
Jim Nasby jimn(at)enterprisedb(dot)com
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Joshua D. Drake 2006-10-06 16:10:06 Re: How to install postgreSQL 8.1.4 on RHEL -ES 4
Previous Message Jay A. Kreibich 2006-10-06 15:37:26 Re: Recursive use