Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 1060F2E349D for ; Fri, 4 Jan 2008 12:26:27 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 30567-06-2 for ; Fri, 4 Jan 2008 12:26:23 -0400 (AST) Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 9E45A2E02EF for ; Fri, 4 Jan 2008 12:26:22 -0400 (AST) Received: from [192.168.1.226] (or-69-34-217-90.sta.embarqhsd.net [69.34.217.90]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m04GQL4Q022381 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Jan 2008 08:26:22 -0800 Message-ID: <477E5E31.1040202@commandprompt.com> Date: Fri, 04 Jan 2008 08:26:25 -0800 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: James Cloos CC: Tom Lane , pgsql-admin@postgresql.org Subject: Re: When does VACUUM FULL not clean out all deleted data? References: <10656.1199426607@sss.pgh.pa.us> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Fri, 04 Jan 2008 08:26:22 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/62 X-Sequence-Number: 27836 James Cloos wrote: >>>>>> "Tom" == Tom Lane writes: > >>> Why was the db using that extra five plus gigs? > > Tom> Smells like a hadn't-been-vacuuming-often-enough problem. > > Sorry, I forgot to mention: autovacuum was enabled and I also ran > this script every night via cron: > > #!/bin/bash > FULL='' > test $(date +%w) -eq 0 && FULL='FULL' > exec psql -U dbm -c "VACUUM ${FULL} VERBOSE ANALYZE" dbm > > The app at least felt faster with the daily vacuum, even though > autovacuum was running. I don't have a good explanation for that, > either. Autovacuum by default won't do enough work for many production databases. You still have to configure it. Joshua D. Drake