From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: SPMLINGAM <spmlingam@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: postgresql performance
Date: Wed, 05 Mar 2008 09:46:05 -0600
Message-ID: <47CE6BDC.EE98.0025.0@wicourts.gov> (raw)
In-Reply-To: <20080305103945.GA3673@uio.no>
References: <15847165.post@talk.nabble.com>
<20080305103945.GA3673@uio.no>
>>> On Wed, Mar 5, 2008 at 4:39 AM, in message <20080305103945.GA3673@uio.no>,
"Steinar H. Gunderson" <sgunderson@bigfoot.com> wrote:
> it's pretty obvious that you
> haven't vacuumed in a very long time. Run VACUUM FULL on your tables
If you use VACUUM FULL, you should probably throw in ANALYZE with
it, and REINDEX, too. An alternative that is probably faster, but
which requires that you have enough free space for a temporary
additional copy of the data, is to CLUSTER the bloated tables,
which automatically takes care of the indexes, but requires a
subsequent ANALYZE.
> regular (non-FULL) VACUUMs or enable autovacuum.
Absolutely!
-Kevin
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: Kevin.Grittner@wicourts.gov, sgunderson@bigfoot.com, spmlingam@gmail.com
Subject: Re: postgresql performance
In-Reply-To: <47CE6BDC.EE98.0025.0@wicourts.gov>
* 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