From: Matthew T. O'Connor <matthew@zeut.net>
To: Rafael Domiciano <rafael.domiciano@gmail.com>
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Rafael Martinez <r.m.guerrero@usit.uio.no>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Vacuum Problems
Date: Wed, 26 Nov 2008 14:54:05 -0500
Message-ID: <492DA95D.3010303@zeut.net> (raw)
In-Reply-To: <3a0028490811260921l5d6aac06v54dca32aae672b97@mail.gmail.com>
References: <3a0028490811260543x74d02719w775a457999cfc74@mail.gmail.com>
<492D5C87.5090505@usit.uio.no>
<3a0028490811260700w6e8d9d86o24effbe0bea2bddb@mail.gmail.com>
<dcc563d10811260740m69f8969bt36be6ae675620dcb@mail.gmail.com>
<3a0028490811260921l5d6aac06v54dca32aae672b97@mail.gmail.com>
Rafael Domiciano wrote:
> I'm not using autovacuum. Regular vacuum goes ok.
> To see the last 10 lines of verbose i will need to run vacuum tonight
>
> If a run a reindex before the vacuum full, increase the "speed" of
> doing vacuum? I found something about it googling.
It might help a bit, but by the end of VACUUM FULL you would need to run
reindex again as VACUUM FULL tends to cause a lot of index bloat. It
is normal for tables to have some slack space, so if you do a regular
vacuum every day (or let autovacuum) it's normal for the table to be a
bit bigger than after a VACUUM FULL, but they should ready steady state
and stop growing.
You may also want to look into using CLUSTER it will rewrite the whole
table and is typically much more efficient that VACUUM FULL, but it
requires 2x disk space while running.
Matt
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: matthew@zeut.net, rafael.domiciano@gmail.com, scott.marlowe@gmail.com, r.m.guerrero@usit.uio.no
Subject: Re: Vacuum Problems
In-Reply-To: <492DA95D.3010303@zeut.net>
* 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