Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 97B38633694 for ; Mon, 4 Jan 2010 20:35:08 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 40475-05 for ; Tue, 5 Jan 2010 00:34:51 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp.iplink.net (smtp.iplink.net [192.139.81.186]) by mail.postgresql.org (Postfix) with ESMTP id 5106A633A83 for ; Mon, 4 Jan 2010 20:34:52 -0400 (AST) Received: from [192.168.1.139] (unknown [64.34.156.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.iplink.net (Postfix) with ESMTP id 790FB9C423A; Mon, 4 Jan 2010 19:34:31 -0500 (EST) Message-ID: <4B428917.3020305@alteeve.com> Date: Mon, 04 Jan 2010 19:34:31 -0500 From: Madison Kelly User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Rosser Schwarz Cc: Steve Crawford , Brad Nicholson , Gary Doades , pgsql-performance@postgresql.org Subject: Re: DB is slow until DB is reloaded References: <4B423D22.7040803@alteeve.com> <4B424215.70605@pinpointresearch.com> <4B424FF6.40207@alteeve.com> <4B425222.7070905@gpdnet.co.uk> <4B425555.6020709@alteeve.com> <1262638856.29852.4.camel@bnicholson-desktop> <4B425E93.1050207@alteeve.com> <4B426359.9040601@pinpointresearch.com> <4B426438.40109@alteeve.com> <37d451f71001041406i3f5d8d5fte8a29cfbc06998c9@mail.gmail.com> In-Reply-To: <37d451f71001041406i3f5d8d5fte8a29cfbc06998c9@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=3.189 tagged_above=-10 required=5 tests=BAYES_50=0.001, FH_DATE_PAST_20XX=3.188 X-Spam-Level: *** X-Archive-Number: 201001/31 X-Sequence-Number: 36911 Rosser Schwarz wrote: > On Mon, Jan 4, 2010 at 2:57 PM, Madison Kelly wrote: >> As for autovacuum, I assumed (yes, I know) that all v8.x releases enabled it >> by default. How would I confirm that it's running or not? > > I believe it's not enabled by default in 8.1-land, and is as of 8.2 > and later. Whether it's running or not, try "SELECT * FROM > pg_autovacuum;". If that returns the null set, it's not doing > anything, as it hasn't been told it has anything to do. > > IME, however, if you really want to benefit from the autovacuum > daemon, you probably do want to be on something more recent than 8.1. > (And, yes, this is a bit of the pot calling the kettle black: I have a > mixed set of 8.1 and 8.3 hosts. Autovacuum is only running on the > latter, while the former are queued for an upgrade.) > > rls You are right, autovacuum is not running after all. From your comment, I am wondering if you'd recommend I turn it on or not? If so, given that I doubt I will upgrade any time soon, how would I enable it? I suppose I could google that, but google rarely shares gotcha's. :) Madi