| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Wei Weng <wweng(at)kencast(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Is there any other way to do this? |
| Date: | 2005-05-18 02:12:35 |
| Message-ID: | 428AA493.4000806@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> This time it worked! But VACUUM FULL requires an exclusive lock on the
> table which I don't really want to grant. So my question is: why is
> VACUUM ANALYZE didn't do the job? Is there any setting I can tweak to
> make a VACUUM without granting a exclusive lock?
You need to run normal vacuum analyze every few minutes or so, to stop
it growing. I suggest pg_autovacuum.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Szűcs Gábor | 2005-05-18 14:30:17 | where+orderby+limit not (always) using appropriate index? |
| Previous Message | Jim C. Nasby | 2005-05-18 00:22:36 | Tuning planner cost estimates |