From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gaetano Mendola <mendola(at)bigfoot(dot)com> |
Cc: | Christopher Browne <cbbrowne(at)acm(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: VACUUM FULL on 24/7 server |
Date: | 2004-10-03 17:23:01 |
Message-ID: | 3380.1096824181@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Gaetano Mendola <mendola(at)bigfoot(dot)com> writes:
> Christopher Browne wrote:
>>> Assuming that the tables in question aren't so large that they cause
>>> mass eviction of buffers, it should suffice to do a plain VACUUM (and
>>> NOT a "VACUUM FULL") on the tables in question quite frequently.
> This is easy to say and almost impraticable. I run a 7.4.5 with the autovacuum:
> pg_autovacuum -d 3 -v 300 -V 0.5 -S 0.8 -a 200 -A 0.8
I'm not very familiar at all with appropriate settings for autovacuum,
but doesn't the above say to vacuum a table only when the dead space
reaches 50%? That seems awfully lax to me. I've always thought one
should vacuum often enough to keep dead space to maybe 10 to 25%.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2004-10-03 17:24:28 | Re: [HACKERS] OT moving from MS SQL to PostgreSQL |
Previous Message | Scott Marlowe | 2004-10-03 17:21:38 | Re: guaranteeing that a sequence never skips |