From: | Richard Neill <rn214(at)cam(dot)ac(dot)uk> |
---|---|
To: | Madison Kelly <linux(at)alteeve(dot)com> |
Cc: | Steve Crawford <scrawford(at)pinpointresearch(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: DB is slow until DB is reloaded |
Date: | 2010-01-04 20:39:13 |
Message-ID: | 4B4251F1.9060700@cam.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> Yup, I even tried manually running 'VACUUM FULL' and it didn't help. As
> for upgrading;
VACUUM FULL is usually considered a bad idea. What you probably want to
do instead is CLUSTER, followed by ANALYZE.
Basically, VACUUM makes the indexes smaller (but doesn't reclaim much
space from the tables themselves). VACUUM FULL reclaims space from the
tables, but bloats the indexes.
> a) I am trying to find a way around the dump/reload. I am doing it as a
> "last resort" only.
> b) I want to keep the version in CentOS' repo.
>
Postgres is pretty easy to build from source. It's nicely
self-contained, and won't bite you with dependency hell. So don't be too
wary of compiling it.
Richard
From | Date | Subject | |
---|---|---|---|
Next Message | Gary Doades | 2010-01-04 20:40:02 | Re: DB is slow until DB is reloaded |
Previous Message | Madison Kelly | 2010-01-04 20:30:46 | Re: DB is slow until DB is reloaded |