From: Joshua D. Drake <jd@commandprompt.com>
To: Geoffrey <lists@serioustechnology.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: When does VACUUM FULL not clean out all deleted data?
Date: Mon, 7 Jan 2008 09:12:11 -0800
Message-ID: <20080107091211.7745b51a@commandprompt.com> (raw)
In-Reply-To: <47824AE7.6000006@serioustechnology.com>
References: <m3lk76du4c.fsf@lugabout.jhcloos.org>
<10656.1199426607@sss.pgh.pa.us>
<m34pdteh7k.fsf@lugabout.jhcloos.org>
<dcc563d10801040902t15784c38vff8c91e3b9207a9c@mail.gmail.com>
<47824AE7.6000006@serioustechnology.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 07 Jan 2008 10:53:11 -0500
Geoffrey <lists@serioustechnology.com> wrote:
> So, I'm wondering if anyone can point me to more specific information
> as to when, if ever, you should 'vacuum full?'
1. If you over run your fsm pages
* Except that vacuum full won't reclaim the index usage so use
CLUSTER instead.
2. If you are only repairing bloat on a smaller table.
* It may be faster to backup and restore the table. Since vacuum full
is an exclusive lock anyway it doesn't matter.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company: Since 1997, http://www.commandprompt.com/
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
SELECT 'Training', 'Consulting' FROM vendor WHERE name = 'CMD'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHgl1rATb/zqfZUUQRAod6AKCUkRKy+gqOkb4xpgVXiP8BCIePKQCgo2yS
ZRmnIVwrYHFoJ8juI08KL6c=
=Jb1i
-----END PGP SIGNATURE-----
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-admin@postgresql.org
Cc: jd@commandprompt.com, lists@serioustechnology.com
Subject: Re: When does VACUUM FULL not clean out all deleted data?
In-Reply-To: <20080107091211.7745b51a@commandprompt.com>
* 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