Re: VACUUM FULL on 24/7 server - Mailing list pgsql-general

From Gaetano Mendola
Subject Re: VACUUM FULL on 24/7 server
Date
Msg-id 4160A0F3.4060806@bigfoot.com
Whole thread Raw
In response to Re: VACUUM FULL on 24/7 server  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: VACUUM FULL on 24/7 server  ("Matthew T. O'Connor" <matthew@zeut.net>)
Re: VACUUM FULL on 24/7 server  ("Matthew T. O'Connor" <matthew@tocr.com>)
List pgsql-general
Tom Lane wrote:
> Gaetano Mendola <mendola@bigfoot.com> writes:
>
>>Christopher Browne wrote:
>>
>>>>Assuming that the tables in question aren't so large that they cause
>>>>mass eviction of buffers, it should suffice to do a plain VACUUM (and
>>>>NOT a "VACUUM FULL") on the tables in question quite frequently.
>
>
>>This is easy to say and almost impraticable. I run a 7.4.5 with the autovacuum:
>
>
>>pg_autovacuum -d 3 -v 300 -V 0.5 -S 0.8 -a 200 -A 0.8
>
>
> I'm not very familiar at all with appropriate settings for autovacuum,
> but doesn't the above say to vacuum a table only when the dead space
> reaches 50%?  That seems awfully lax to me.  I've always thought one
> should vacuum often enough to keep dead space to maybe 10 to 25%.

The problem is that I can not set these value per table and per database
so, I had to find some compromise, however I will test in the next days
what happen with -V 0.2

However each six hour I perform a vacuum on all database and the HD space
continue to grow even with FSM parameters large enough.

I'll post in a couple of day about the new settings.

Regards
Gaetano Mendola





pgsql-general by date:

Previous
From: Mike Nolan
Date:
Subject: Re: guaranteeing that a sequence never skips (fwd)
Next
From: "Matthew T. O'Connor"
Date:
Subject: Re: VACUUM FULL on 24/7 server