| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Matthew T(dot) OConnor" <matthew(at)zeut(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Mario Weilguni" <mario(dot)weilguni(at)icomedias(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: possible vacuum improvement? |
| Date: | 2002-09-04 03:47:49 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOIEAOCEAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I have been doing some poking around with this item, and I was
> planning on
> using the stats collector to do "intelligent" auto-vacuuming. I
> was planning
> on adding some new columns that account for activity that has taken place
> since the last vacuum. The current stats collector shows n_tup_ins,
> n_tup_upd and n_tup_del for any given rel, but those numbers have
> nothing to
> do with what has happened since the last vacuum, hence nothing to do with
> current status or need for vacuum.
Postgres 7.3-beta has a new function 'pg_stat_reset()' that you can call to reset the stats collector after a vacuum...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew T. OConnor | 2002-09-04 04:00:03 | Re: possible vacuum improvement? |
| Previous Message | Matthew T. OConnor | 2002-09-04 03:44:58 | Re: possible vacuum improvement? |