From: Shoaib Mir <shoaibmir@gmail.com>
To: Ruben Rubio <ruben@rentalia.com>
Cc: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Vacuum full is slow
Date: Mon, 19 Mar 2007 19:37:41 +0500
Message-ID: <bf54be870703190737x40b5e630y9b1673aad95ff4ac@mail.gmail.com> (raw)
In-Reply-To: <45FE9C4B.7070602@rentalia.com>
References: <45FE6DD4.7080304@rentalia.com>
<45FE72A3.5020709@enterprisedb.com>
<45FE9C4B.7070602@rentalia.com>
>>vacuum_cost_delay = 100
>>No idea how long will take normal vacuum. I ll try tonight when there is
>>not too much load.
That can really take the VACUUM a long time to complete, but you might want
to have it there as it will be good for performance by setting it a little
high in a high OLTP environment.
I will recommend setting it to 0 first and then you can start moving it high
as per your needs...
--
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 3/19/07, Ruben Rubio <ruben@rentalia.com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> >
> > You don't have vacuum_cost_delay set, do you? How long does normal
> > vacuum run?
>
> vacuum_cost_delay = 100
> No idea how long will take normal vacuum. I ll try tonight when there is
> not too much load.
>
> >
> > The manual suggests dropping all indexes before running vacuum full, and
> > recreating them afterwards. That's worth trying.
> >
>
> I ll try that also. Is there any way to do it? Do i have to delete /
> create each one manually?
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFF/pxLIo1XmbAXRboRAjR1AJ9V4kBDCd++HSmUm8+ZCLs2RY0xnACfZ7Mp
> uBC031TFhO2NGOihfWPAQQ8=
> =QCYi
> -----END PGP SIGNATURE-----
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
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-performance@postgresql.org
Cc: shoaibmir@gmail.com, ruben@rentalia.com, heikki@enterprisedb.com
Subject: Re: Vacuum full is slow
In-Reply-To: <bf54be870703190737x40b5e630y9b1673aad95ff4ac@mail.gmail.com>
References: <45FE6DD4.7080304@rentalia.com> <45FE72A3.5020709@enterprisedb.com> <45FE9C4B.7070602@rentalia.com> <bf54be870703190737x40b5e630y9b1673aad95ff4ac@mail.gmail.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