Re: Postgresql backend to perform vacuum automatically - Mailing list pgsql-hackers

From mlw
Subject Re: Postgresql backend to perform vacuum automatically
Date
Msg-id 3C852F5A.225E57E9@mohawksoft.com
Whole thread Raw
In response to Re: Postgresql backend to perform vacuum automatically  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Postgresql backend to perform vacuum automatically  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian wrote:
> 
> mlw wrote:
> > Bruce Momjian wrote:
> > >
> > > Tom Lane wrote:
> > > > Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > > > > Yes, I am seeing only zeros too.  Jan?
> > > >
> > > > Did you turn on statistics gathering?  See the Admin Guide's discussion
> > > > of database monitoring.
> > >
> > > Oops, now I remember.  Those are off by default and only the query
> > > string is on by default.  Thanks.
> >
> > This raises the question, by turning these on, does that affect database
> > performance?
> >
> > If so, it may not be the answer for a selective vacuum.
> >
> > If they do not affect performance, then why have them off?
> 
> I think Jan said 2-3%.  If we can get autovacuum from it, it would be a
> win to keep it on all the time, perhaps.

Assuming that the statistics get updated:

How often should the sats table be queried?
What sort of configurability would be needed?


pgsql-hackers by date:

Previous
From: F Harvell
Date:
Subject: Re: Database Caching
Next
From: Bruce Momjian
Date:
Subject: Re: Postgresql backend to perform vacuum automatically