Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 0536A9FB1DF; Wed, 27 Sep 2006 15:33:18 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 84266-03; Wed, 27 Sep 2006 18:32:59 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by postgresql.org (Postfix) with ESMTP id AEF8A9FA7BA; Wed, 27 Sep 2006 15:32:59 -0300 (ADT) Received: from pool-72-88-194-29.nwrknj.fios.verizon.net ([72.88.194.29] helo=[192.168.4.67]) by outbound.mailhop.org with esmtpa (Exim 4.51) id 1GSeDJ-000NQ9-6I; Wed, 27 Sep 2006 14:32:57 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 72.88.194.29 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: tocr Message-ID: <451AC3E6.5050108@zeut.net> Date: Wed, 27 Sep 2006 14:33:10 -0400 From: "Matthew T. O'Connor" User-Agent: Thunderbird 2.0a1 (Windows/20060724) MIME-Version: 1.0 To: Csaba Nagy CC: Edoardo Ceccarelli , postgres performance list , pgsql-admin@postgresql.org Subject: Re: [PERFORM] autovacuum on a -mostly- r/o table References: <451AA1FE.9050704@axa.it> <1159373624.3874.187.camel@coppola.muc.ecircle.de> In-Reply-To: <1159373624.3874.187.camel@coppola.muc.ecircle.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200609/333 X-Sequence-Number: 23247 Csaba Nagy wrote: > On Wed, 2006-09-27 at 18:08, Edoardo Ceccarelli wrote: > >> How can I configure the vacuum to run after the daily batch insert/update? >> > > Check out this: > http://www.postgresql.org/docs/8.1/static/catalog-pg-autovacuum.html > > By inserting the right row you can disable autovacuum to vacuum your big > tables, and then you can schedule vacuum nightly for those just as > before. There's still a benefit in that you don't need to care about > vacuuming the rest of the tables, which will be done just in time. In addition autovacuum respects the work of manual or cron based vacuums, so if you issue a vacuum right after a daily batch insert / update, autovacuum won't repeat the work of that manual vacuum.