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

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Kevin Johnson <Kevin(dot)Johnson(at)noaa(dot)gov>
Cc: Jim Nasby <jimn(at)enterprisedb(dot)com>, 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
Date: 2006-10-06 19:01:34
Message-ID: 20061006190134.GA6084@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Fri, Oct 06, 2006 at 06:39:40 -0400,
Kevin Johnson <Kevin(dot)Johnson(at)noaa(dot)gov> 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.

The other thing you need to watch out for is that your FSM setting is
large enough to recover all of the dead space. If your vacuum runs aren't
recovering as much dead space as is being created on average, then you are
going to have dead space accumalate.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Wolfgang Schedl 2006-10-07 05:35:18 Cant connect to psql on winxp
Previous Message Chris Browne 2006-10-06 18:04:01 Re: Recursive use