From: Richard Neill <rn214@cam.ac.uk>
To: Madison Kelly <linux@alteeve.com>
Cc: Steve Crawford <scrawford@pinpointresearch.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: DB is slow until DB is reloaded
Date: Mon, 04 Jan 2010 20:39:13 +0000
Message-ID: <4B4251F1.9060700@cam.ac.uk> (raw)
In-Reply-To: <4B424FF6.40207@alteeve.com>
References: <4B423D22.7040803@alteeve.com>
<4B424215.70605@pinpointresearch.com>
<4B424FF6.40207@alteeve.com>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: rn214@cam.ac.uk, linux@alteeve.com, scrawford@pinpointresearch.com
Subject: Re: DB is slow until DB is reloaded
In-Reply-To: <4B4251F1.9060700@cam.ac.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox