X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id BF86A9FA2FA for ; Thu, 25 May 2006 23:21:03 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 15217-01 for ; Thu, 25 May 2006 23:20:57 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by postgresql.org (Postfix) with ESMTP id 78C229F9B14 for ; Thu, 25 May 2006 23:20:57 -0300 (ADT) Received: from ool-45745d9b.dyn.optonline.net ([69.116.93.155] helo=[192.168.4.67]) by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.51) id 1FjRwc-0003pq-Pp; Thu, 25 May 2006 22:20:54 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 69.116.93.155 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: zeut Message-ID: <447665FE.5010905@zeut.net> Date: Thu, 25 May 2006 22:20:46 -0400 From: "Matthew T. O'Connor" User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Tom Lane , Benjamin Krajmalnik , pgsql-admin@postgresql.org, "Matthew T. O'Connor" Subject: Re: pg_clog questions References: <8511B4970E0D124898E973DF496F9B432516E3@stash.stackdump.local> <15596.1148588444@sss.pgh.pa.us> <20060525204319.GL13700@surnet.cl> In-Reply-To: <20060525204319.GL13700@surnet.cl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/372 X-Sequence-Number: 21904 Alvaro Herrera wrote: > Tom Lane wrote: >> Hm. I believe that autovac only does database-wide vacuums when it >> thinks they're necessary to prevent transaction wraparound failures. >> Which would mean that it'd let pg_clog grow to something on the order >> of half a gig before any truncation would happen. That's probably >> insufficiently aggressive :-( >> >> Alvaro, Matthew, any thoughts about improving that? Not really. Alvara mentioned reducing the constant that we test against for DB wide vacuum. I'm a little concerned that might result is database-wide vacuums more often than desired, but I don't see a better answer off the top of my head.