Re: after vacuum, db is still "growing" :(

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: pgsql-general(at)postgresql(dot)org
Cc: gabor <gabor(at)nekomancer(dot)net>
Subject: Re: after vacuum, db is still "growing" :(
Date: 2005-12-09 16:30:06
Message-ID: 20051209163005.GD20352@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Dec 09, 2005 at 10:00:45AM +0100, Rafael Martinez Guerrero wrote:
> On Fri, 2005-12-09 at 08:45, gabor wrote:
> [...........]
> >
> > are there any cases, where a normal vacuum is unable to reclaim some
> > space
>
> Hello
>
> We have det same problem in some databases running 7.4.8. Having
> max_fsm_pages and max_fsm_relations properly configurated does not help.
>
> It looks like this happens in tables with data that is updated/deleted
> very often and that the files growing are the ones for the indexes, when
> using B-trees.

More recent versions do reuse index space much better than before. And
on busy tables you need to vacuum very regularly. In recent versions
you have an autovacuum daemon to handle much of this for you...

Have a ncie day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message William 2005-12-09 16:33:35 PgSQL 8.1.0 Solaris w/ Sun's cc
Previous Message Jan Wieck 2005-12-09 16:22:48 Re: bug or not? Trigger preventing delete causes circumvention