| From: | Rich Cullingford <rculling(at)sysd(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | pre-Vacuum statistics |
| Date: | 2003-07-10 18:19:26 |
| Message-ID: | 3F0DAE2E.3020102@sysd.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Greetings,
All the recommendations I can locate concerning the use of (the various
flavors of) VACUUM suggest running it at regular intervals. Is there any
way, for a given table, to discover how many/what percentage of rows are
likely to be VACUUMable at a given point, so that some kind of
threshold-based VACUUM could be done by an application? We have several
tables that undergo bursty UPDATEs, where large numbers of transactions
occur "relatively" infrequently; and others where the UPDATEs occur at
regular intervals (a few seconds or so).
Thanks for any advice!
Regards,
Rich Cullingford
rculling(at)sysd(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sean Chittenden | 2003-07-10 20:22:07 | Re: [PERFORM] Extreme high load averages |
| Previous Message | alexandre arruda paes :: aldeia digital | 2003-07-10 17:43:25 | Dual Xeon + HW RAID question |