|
Home > Archive > PostgreSQL Administration > October 2006 > Re: Disk space consumed by pk not returned after vacuum or
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Disk space consumed by pk not returned after vacuum or
|
|
| Kevin Johnson 2006-10-25, 8:24 am |
| 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:
> | |
| Bruno Wolff III 2006-10-25, 8:24 am |
| On Fri, Oct 06, 2006 at 06:39:40 -0400,
Kevin Johnson <Kevin.Johnson@noaa.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.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
|
|
|
|
|