From: | "Roderick A(dot) Anderson" <raanders(at)tincan(dot)org> |
---|---|
To: | Jan Wieck <janwieck(at)yahoo(dot)com> |
Cc: | Carsten Gerhardt <carsten(dot)gerhardt(at)ppi(dot)de>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: When do I Vacuum ? |
Date: | 2001-12-07 17:55:28 |
Message-ID: | Pine.LNX.4.10.10112070948530.29916-100000@tincan.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 7 Dec 2001, Jan Wieck wrote:
> The question how often to vacuum depends on the database use.
> As a rule of thumb I'd suggest start with vacuuming when
> approx. 10-30% of the data has been touched (UPDATED/DELETED)
Which brings up an interesting thought. Is there any way to query the
databae and find out how much data has been 'CHANGED' since the last
vacuum? I don't remember seeing any mention of this for a year or
longer in either GENERAL or HACKERS.
If there is or could be, a low usage database could be probed and
then vacumm run if needed. Not sure if the CPU cycles to run the cron
job and query are lower than the 'just do it' on a set schedule would
be.
Cheers,
Rod
--
Let Accuracy Triumph Over Victory
Zetetic Institute
"David's Sling"
Marc Stiegler
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2001-12-07 18:05:42 | Re: Trigger problem |
Previous Message | Tom Lane | 2001-12-07 17:38:03 | Re: Using Cursor in PostgreSQL 7.2 |