| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | mlw <markw(at)mohawksoft(dot)com> |
| 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:59:08 |
| Message-ID: | 200203052059.g25Kx8R20024@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > > 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?
You could wake up every few minutes and see how the values have changed.
I don't remember if there is a way to clear that stats so you can see
just the changes in the past five minutes. Vacuum the table that had
activity.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dann Corbit | 2002-03-05 21:16:28 | Re: Postgresql backend to perform vacuum automatically |
| Previous Message | mlw | 2002-03-05 20:49:30 | Re: Postgresql backend to perform vacuum automatically |