| From: | Neil Padgett <npadgett(at)redhat(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | mlw <markw(at)mohawksoft(dot)com>, 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 21:42:25 |
| Message-ID: | 1015364560.2497.0.camel@totally-bodacious |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2002-03-05 at 15:59, Bruce Momjian wrote:
> > > > 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.
Ick -- polling. The statistics process should be able to wake somebody
up / notify the postmaster when the statistics change such that a vacuum
is required.
Neil
--
Neil Padgett
Red Hat Canada Ltd. E-Mail: npadgett(at)redhat(dot)com
2323 Yonge Street, Suite #300,
Toronto, ON M4P 2C9
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-03-05 21:54:47 | Re: Postgresql backend to perform vacuum automatically |
| Previous Message | Domingo Alvarez Duarte | 2002-03-05 21:22:25 | Re: timestamp_part() bug? |