From: Michael Stone <mstone+postgres@mathom.us>
To: Tomeh, Husam <htomeh@firstam.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: "Vacuum Full Analyze" taking so long
Date: Mon, 25 Jul 2005 17:30:58 -0400
Message-ID: <20050725213058.GQ19080@mathom.us> (raw)
In-Reply-To: <C45835824D00A844BBD0F032D5CDED920116DC10@pisgana01sxch01.ana.firstamdata.com>
References: <C45835824D00A844BBD0F032D5CDED920116DC10@pisgana01sxch01.ana.firstamdata.com>
I'd say, "don't do that". Unless you've deleted a lot of stuff and are
expecting the DB to shrink, a full vacuum shouldn't really be needed. On
a DB that big a full vacuum is just going to take a long time. If you
really are shrinking, consider structuring things so you can just drop a
table instead of vacuuming it (the drop is fairly instantaneous). If you
can't do that, consider dropping the indices, vacuuming, and recreating
the indices.
Mike Stone
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: mstone+postgres@mathom.us, htomeh@firstam.com
Subject: Re: "Vacuum Full Analyze" taking so long
In-Reply-To: <20050725213058.GQ19080@mathom.us>
* 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