X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id BE5318B9EBC for ; Wed, 23 Feb 2005 19:16:19 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 03283-09 for ; Wed, 23 Feb 2005 19:16:11 +0000 (GMT) Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by svr1.postgresql.org (Postfix) with ESMTP id C50688B9E80 for ; Wed, 23 Feb 2005 19:16:11 +0000 (GMT) Received: from ool-4350c7ad.dyn.optonline.net ([67.80.199.173] helo=[192.168.0.66]) by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.44) id 1D41zV-0001vD-Qm; Wed, 23 Feb 2005 14:16:09 -0500 Message-ID: <421CD6F0.8010406@zeut.net> Date: Wed, 23 Feb 2005 14:18:08 -0500 From: "Matthew T. O'Connor" Organization: Terrie O'Connor Realtors User-Agent: Mozilla Thunderbird 1.0RC1 (Windows/20041201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christopher Browne Cc: pgsql-performance@postgresql.org Subject: Re: is pg_autovacuum so effective ? References: <12400.1109107683@sss.pgh.pa.us> <421BD64E.30803@bigfoot.com> <60psyr265t.fsf@dba2.int.libertyrms.com> In-Reply-To: <60psyr265t.fsf@dba2.int.libertyrms.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mail-Handler: MailHop Outbound by DynDNS.org X-Originating-IP: 67.80.199.173 X-Report-Abuse-To: abuse@dyndns.org (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: zeut X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.012 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/335 X-Sequence-Number: 10664 Christopher Browne wrote: >Gaetano Mendola writes: > > >>I do a graph about my disk usage and it's a ramp since one week, >>I'll continue to wait in order to see if it will decrease. >>I was expecting the steady state at something like 4 GB >>( after a full vacuum and reindex ) + 10 % = 4.4 GB >>I'm at 4.6 GB and increasing. I'll see how it will continue. >> >> > >You probably want for the "experiment" to last more than a week. > >After all, it might actually be that with your usage patterns, that >table would stabilize at 15% "overhead," and that might take a couple >or three weeks. > >Unless it's clear that it's growing perilously quickly, just leave it >alone so that there's actually some possibility of reaching an >equilibrium. Any time you "VACUUM FULL" it, that _destroys_ any >experimental results or any noticeable patterns, and it guarantees >that you'll see "seemingly perilous growth" for a while. > >And if the table is _TRULY_ growing "perilously quickly," then it is >likely that you should add in some scheduled vacuums on the table. >Not VACUUM FULLs; just plain VACUUMs. > >I revised cron scripts yet again today to do hourly and "4x/day" >vacuums of certain tables in some of our systems where we know they >need the attention. I didn't schedule any VACUUM FULLs; it's >unnecessary, and would lead directly to system outages, which is >totally unacceptable. > > Chris, is this in addition to pg_autovacuum? Or do you not use pg_autovacuum at all?, and if so why not?