Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 654E26501E0 for ; Fri, 31 Oct 2008 15:32:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 08977-04 for ; Fri, 31 Oct 2008 15:31:57 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from po-out-1718.google.com (po-out-1718.google.com [72.14.252.157]) by postgresql.org (Postfix) with ESMTP id AEF58650177 for ; Fri, 31 Oct 2008 15:31:57 -0300 (ADT) Received: by po-out-1718.google.com with SMTP id y22so7743375pof.3 for ; Fri, 31 Oct 2008 11:31:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=nvFjnXO9XRNmajwHT5Isb805KZHzMiPZfqnrCQCGoKs=; b=Ha6mcpW9S7IQ0FjgDNk5YQTRZjEH6S0xZWLGQwmIQQ1bgqmxHVt1AFJjq2GbUoJyZz HaH95sii+mwyYBf4HqD+dio7rxng3eTFyT0DNVXDQ1g4r4Eb4rsE4ZXqdUx6hR2NAbXn EMd0BvdBBTnox1MgeDp+K527kuf/rbAFU+FgE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=j6fOsltXmowldJsJRNuq6Rhmlb4BQL+eyhBMYb/GlTZYR6GTOFL9CnhuLVjTn2xj9n 0wV7CQdg5LZyCkm3pCiZO7oxVBO6fTT0T1aYhe25hCej6wyTgo4TH3B3VHPUpTvo/oIB b8rjqDsliavQOKESpIhP+qppgJvZMzXnJ013o= Received: by 10.114.168.1 with SMTP id q1mr10265886wae.72.1225477916430; Fri, 31 Oct 2008 11:31:56 -0700 (PDT) Received: by 10.114.39.11 with HTTP; Fri, 31 Oct 2008 11:31:56 -0700 (PDT) Message-ID: Date: Fri, 31 Oct 2008 12:31:56 -0600 From: "Scott Marlowe" To: "Alvaro Herrera" Subject: Re: autovacuum questions Cc: "Rafael Domiciano" , isabella.ghiurea@nrc-cnrc.gc.ca, pgsql-admin@postgresql.org In-Reply-To: <20081031160213.GC10668@alvh.no-ip.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <490B2161.1070502@nrc-cnrc.gc.ca> <3a0028490810310832t2972fb95l6c8d01e7895c1b6c@mail.gmail.com> <20081031160213.GC10668@alvh.no-ip.org> 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: 200810/197 X-Sequence-Number: 30653 On Fri, Oct 31, 2008 at 10:02 AM, Alvaro Herrera wrote: > Rafael Domiciano escribi=F3: > >> The vacuum is not full, to run a full vacuum you need to set a cron job; >> better to run at the night. > > Doing VACUUM FULL on crontab is rarely a good idea. If you find > yourself in a situation where you need VACUUM FULL, then you've not > tuned regular vacuum appropriately. There are some use cases where vacuum full is appropriate. But they're rare. And they're usually better off being added to whatever script is doing the thing that causes the database to need vacuum full. Certain batch processing or data loading processes need vacuum full and or reindex when finishing. But the common thought process on vacuum full for most people is "If vacuum is good, vacuum full must be even better!" which is just wrong.