From: | mlw <markw(at)mohawksoft(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nicolas Bazin <nbazin(at)ingenico(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Postgresql backend to perform vacuum automatically |
Date: | 2002-03-05 20:49:30 |
Message-ID: | 3C852F5A.225E57E9@mohawksoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
>
> mlw wrote:
> > Bruce Momjian wrote:
> > >
> > > Tom Lane wrote:
> > > > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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?
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-03-05 20:59:08 | Re: Postgresql backend to perform vacuum automatically |
Previous Message | F Harvell | 2002-03-05 19:59:45 | Re: Database Caching |