Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id DFDA42E00BA for ; Fri, 14 Mar 2008 21:52:00 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 71636-01 for ; Fri, 14 Mar 2008 21:51:57 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mailout.abaca.com (mailout.abaca.com [75.59.196.2]) by postgresql.org (Postfix) with ESMTP id D3DC92E00B5 for ; Fri, 14 Mar 2008 21:51:57 -0300 (ADT) Received: from v-abaca-epg.lab.abaca.com (localhost.localdomain [127.0.0.1]) by v-abaca-epg.lab.abaca.com (Postfix-out) with ESMTP id CF87E11008E; Fri, 14 Mar 2008 17:55:21 -0700 (PDT) X-Propel-Return-Path: Received: from mailout.abaca.com ([172.16.83.19]) by [127.0.0.1] ([127.0.0.1]) (port 7027) (Abaca EPG outproxy filter 3.1.0.8749 $Rev: 8725 $) id 5uNZr83f0Tl0; Fri, 14 Mar 2008 17:55:21 -0700 Received: from mail.abaca.com (unknown [172.16.83.4]) by v-abaca-epg.lab.abaca.com (Postfix-out) with ESMTP id B19DA11007E; Fri, 14 Mar 2008 17:55:21 -0700 (PDT) Received: from [172.16.83.73] (172.16.83.73) by mail.abaca.com (172.16.83.4) with Microsoft SMTP Server id 8.0.744.0; Fri, 14 Mar 2008 17:52:46 -0700 Subject: Re: best way to run maintenance script From: Vinubalaji Gopal To: "Joshua D. Drake" CC: "Pgsql-Performance ((E-mail))" In-Reply-To: <20080314173235.58f854e6@commandprompt.com> References: <1205542821.12661.16.camel@vinu-ubuntu.abaca> <20080314173235.58f854e6@commandprompt.com> Content-Type: text/plain Date: Fri, 14 Mar 2008 17:51:52 -0800 Message-ID: <1205545912.12661.22.camel@vinu-ubuntu.abaca> MIME-Version: 1.0 X-Mailer: Evolution 2.12.1 Content-Transfer-Encoding: 7bit X-Propel-ID: 5uNZr83f0Tl0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200803/323 X-Sequence-Number: 29277 Hi Joshua, > You can use parameters such as vacuum_cost_delay to help this... see > the docs: > > http://www.postgresql.org/docs/8.3/static/runtime-config-autovacuum.html I am checking it out. Seems to be a nice option for vacuum - but wish there was a way to change the delete priority or I will try to use the C based priority hack. > If you are truly running 8.0 and not something like 8.0.15 vacuum is > the least of your worries. Its 8.0.4. Thanks. -- Vinu