Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id CCA1B6347C9 for ; Tue, 31 Mar 2009 13:20:39 -0300 (ADT) 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 51630-03-2 for ; Tue, 31 Mar 2009 13:20:32 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by mail.postgresql.org (Postfix) with ESMTP id 6F201634268 for ; Tue, 31 Mar 2009 13:20:30 -0300 (ADT) Received: by ey-out-2122.google.com with SMTP id 22so484376eye.61 for ; Tue, 31 Mar 2009 09:20:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=B/SObreJ1aWB/JY5+P8C/W/pjlWmwPgb8fuVbfsXs9Q=; b=GXXpzf0vN+Lp0HR027e4H+O3HFQlrbbLmqAAGCgmlXMxIhTtKaM897++labSXtrvCt hR4dV2rIoAy6kGG4eqTG9QNVrqdGw1jwlV9f54k2owhnUrrlRSAnNBphqowYtdImwBhx gJUHK6pLyklEQ81daeqOkiNvyBPDdN91iE/y0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Mgxzwnd+XC73kdSxJMeVgMJ5PsqI3dDl+oCvbokk3n3aYbcf6t1+MUdG9JuEZ7eS5M CWl4MSY08Sh6wS+cwmbsy2PbfbQWi2mH9dPugUuzc3qIG7VQDb9h6OL/gZxPENCc7u68 yyTZISa55W0du36Va7IwuXUdxCvgCCyndih30= MIME-Version: 1.0 Received: by 10.210.128.10 with SMTP id a10mr3669518ebd.11.1238516429221; Tue, 31 Mar 2009 09:20:29 -0700 (PDT) In-Reply-To: <3a0028490903310904q3df73b6dob4d62511df38563c@mail.gmail.com> References: <3a0028490903310904q3df73b6dob4d62511df38563c@mail.gmail.com> Date: Tue, 31 Mar 2009 10:20:29 -0600 Message-ID: Subject: Re: Vacuum Full From: Scott Marlowe To: Rafael Domiciano Cc: "pgsql-admin@postgresql.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.014 tagged_above=0 required=5 tests=AWL=0.014 X-Spam-Level: X-Archive-Number: 200903/269 X-Sequence-Number: 31769 On Tue, Mar 31, 2009 at 10:04 AM, Rafael Domiciano wrote: > Hello People, > > I have some doubts about Vacuum Full. There We go: > 1) The Only thing that Vacuum Full (Only Full, not Analyze) is to clean > "dead space" on the disc, and reorganize the relation at the physical level? > If it's true, so doing this may speed up select's, while the Postgres will > going to do less hit in the disc. I'm right? Generally speaking, vacuum full should not normally be needed. Regular vacuuming should free up enough free space that the table reaches an equilibrium where it has some small percentage of available space (5 to 15% or so) and stay there. > 2) Doing only Vacuum Analyze I have a enlargement of the parameter > max_fsm_pages. Does it have any impact in the operation? > Should I increment the value in the conf to be so large than the Vacuum > Verbose shows me? If the needed fsm settings need to keep increasing then something is wrong. > 3) There are differences in performace of Vacuum Full between versions 8.1.4 > and 8.3.7? > As soon as possible we are going to migrate the Postgres to 8.3.7, just > waiting the finish of the tests of the software in the new version. Yeah, 8.3 is faster. > 4) The right way to run Vacuum and Reindex is: Vacuum and Reindex or Reindex > and Vacuum? > Running Vacuum I have a Index Bloat, right?! So I have to run Reindex afet > Vacuum?! > If true I'll change the script to make first Vacuum and then Reindex. yep, vacuum full, then reindex. > 5) Does have any way to see how much is left to finish vacuum? Not that I know of. I notice you don't mention autovacuum. Are you running it? And if not, why not?