Re: Database size Vs performance degradation - Mailing list pgsql-performance

From Tom Lane
Subject Re: Database size Vs performance degradation
Date
Msg-id 25537.1217430316@sss.pgh.pa.us
Whole thread Raw
In response to Re: Database size Vs performance degradation  ("Dave North" <DNorth@signiant.com>)
List pgsql-performance
"Dave North" <DNorth@signiant.com> writes:
> From: Richard Huxton [mailto:dev@archonet.com]
>> Well, that's pretty much the definition of bloat. Are you sure you're
>> vacuuming enough?

> DN: Well, the auto-vac is kicking off pretty darn frequently...around
> once every 2 minutes.  However, you just made me think of the obvious -
> is it actually doing anything?!  The app is pretty darn write intensive
> so I wonder if it's actually able to vacuum the tables?

IIRC, the default autovac parameters in 8.1 were pretty darn
unaggressive.  You should also check for long-running transactions
that might be preventing vacuum from removing recently-dead rows.

One of the reasons for updating off 8.1 is that finding out what autovac
is really doing is hard :-(.  I think it does log, but at level DEBUG2
or so, which means that the only way to find out is to accept a huge
amount of useless chatter in the postmaster log.  Newer releases have
a saner logging scheme.

            regards, tom lane

pgsql-performance by date:

Previous
From: "Dave North"
Date:
Subject: Re: Database size Vs performance degradation
Next
From: Craig James
Date:
Subject: Re: Database size Vs performance degradation