Re: Vacuuming on heavily changed databases

On Mon, May 19, 2008 at 08:38:09PM +0200, Scott Marlowe wrote:
> OK. Assuming that the 50G is mostly dead space, there are a few
> possibilities that could be biting you here, but the most likely one
> is that your Free Space Map settings aren't high enough to include all
> the rows that have been deleted since the last vacuum was run. If you
> can't take down the server to change those settings, then running
> vacuum more often will help.
>
> The autovacuum daemon is your friend. Even with the default non
> aggresive settings it comes with, it would have caught this long
> before now.

I can bring down the DB for short time, but I am stuct with 8.0. Found
that autovacuum is part of contrib, thus will try

Thank you all for the opinion

Regards,
Bohdan