From: | Hannes Dorbath <light(at)theendofthetunnel(dot)de> |
---|---|
To: | "Joey K(dot)" <pguser(at)gmail(dot)com> |
Subject: | Re: Question about VACUUM |
Date: | 2008-10-25 15:46:03 |
Message-ID: | 49033F3B.3050807@theendofthetunnel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Joey K. wrote:
>> Is it possible to estimate how long VACUUM on a table might take?
>
>> The table size is growing as "VACUUM" is being performed. I assume I need
> reindex after VACUUM is complete.
>
>> I run VACUUM from psql and I Ctrl-C it to turn it off is this acceptable?
>
>> maintenance_work_mem is at 64MB and shared_buffers at 2GB. Should I
> dedicate more memory to maintenance_work_mem to speedup VACUUM?
>
> The server is a Intel Xeon 3.0GHz with 4GB RAM and RAID-5 (Yes I know).
>
> Thanks in advance,
> Steve
Hello Joey,
an alternative to vacuum might be to use cluster on the big tables. The
documentation on that feature is here:
http://www.postgresql.org/docs/8.3/static/sql-cluster.html
To my knowledge vacuum full might add to index bloat, I'm not sure about
plain vacuum. I'd increase maintenance_work_mem to at least 256 MB and
lower shared_buffers a bit.
It should be OK to Ctrl-C a vacuum task in psql.
--
Best regards,
Hannes Dorbath
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-10-25 16:04:01 | Re: again... |
Previous Message | Joey K. | 2008-10-25 15:21:40 | Question about VACUUM |