From: Alvaro Herrera <alvherre@commandprompt.com>
To: Nolan Cafferky <Nolan.Cafferky@rbsinteractive.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: VACUUM ANALYZE suddenly taking forever
Date: Thu, 27 Jul 2006 11:31:43 -0400
Message-ID: <20060727153143.GA18774@surnet.cl> (raw)
In-Reply-To: <44C8DB88.80708@rbsinteractive.com>
References: <44C8DB88.80708@rbsinteractive.com>
Nolan Cafferky wrote:
> The so far untried ideas I've had are:
>
> * Try out the autovacuum service
> * Re-index tables (this hasn't been done for at least months, maybe never)
> * Do some selective VACUUM FULL on high-use tables (materialized view
> for report seems like a likely culprit, but also seems like it wouldn't
> influence both databases)
> * Restart postgres, restart the machine itself, and other useless handwaving
* Check whether there are open, idle transactions and close them
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: alvherre@commandprompt.com, Nolan.Cafferky@rbsinteractive.com
Subject: Re: VACUUM ANALYZE suddenly taking forever
In-Reply-To: <20060727153143.GA18774@surnet.cl>
References: <44C8DB88.80708@rbsinteractive.com> <20060727153143.GA18774@surnet.cl>
* 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