Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 81CDA9FB8C8 for ; Mon, 19 Mar 2007 11:37:50 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 26347-03 for ; Mon, 19 Mar 2007 11:37:43 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.248]) by postgresql.org (Postfix) with ESMTP id 1BCDA9FB31E for ; Mon, 19 Mar 2007 11:37:42 -0300 (ADT) Received: by an-out-0708.google.com with SMTP id c24so1205930ana for ; Mon, 19 Mar 2007 07:37:41 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=S12hIAbTSgI26jMzhf1lt61yd8y+7p+F2Uup2PnKfFTqG51rsj9H4yo54yJXtbf45ENp1dqy1fDZjKDUgX+bDYNv59HkbJQmUr7P9a5ExcgvpJG7QYDZXWqIr8wvJnx3QLxroM1l54S7PpTgFKWxRmSUb2e1uc6gyfkVuxtC9Yk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Yu6KDYtlXXTBLwF2G9zvKhqAIaA/MdXJskxPCOU9twm79HabAqoUckzUHomIC2H6CBGiWQJycMihfwZP2GZ44bWi7UNEkeTJDHpBve9X0LXVCB4NLeSAPSV0Fb8N7sGnmfQpbuIWtRvQQOAdonnVHu0evR3/5oyAQnjDoSY4dxY= Received: by 10.100.96.2 with SMTP id t2mr1385928anb.1174315061658; Mon, 19 Mar 2007 07:37:41 -0700 (PDT) Received: by 10.100.38.6 with HTTP; Mon, 19 Mar 2007 07:37:41 -0700 (PDT) Message-ID: Date: Mon, 19 Mar 2007 19:37:41 +0500 From: "Shoaib Mir" To: "Ruben Rubio" Subject: Re: Vacuum full is slow Cc: "Heikki Linnakangas" , pgsql-performance@postgresql.org In-Reply-To: <45FE9C4B.7070602@rentalia.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_90648_27727372.1174315061542" References: <45FE6DD4.7080304@rentalia.com> <45FE72A3.5020709@enterprisedb.com> <45FE9C4B.7070602@rentalia.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/278 X-Sequence-Number: 23683 ------=_Part_90648_27727372.1174315061542 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline >>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 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 > ------=_Part_90648_27727372.1174315061542 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline >>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

------=_Part_90648_27727372.1174315061542--