X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id CC83D11F66E0 for ; Fri, 31 Mar 2006 19:45:19 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 58179-07 for ; Fri, 31 Mar 2006 19:45:19 -0400 (AST) 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 E2FF711F66DC for ; Fri, 31 Mar 2006 19:45:16 -0400 (AST) Received: from ool-4350c8e6.dyn.optonline.net ([67.80.200.230] helo=[192.168.0.96]) by outbound.mailhop.org with esmtpa (Exim 4.51) id 1FPTIq-0007AI-EY; Fri, 31 Mar 2006 18:45:16 -0500 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 67.80.200.230 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: <442DBF22.6090303@zeut.net> Date: Fri, 31 Mar 2006 18:45:38 -0500 From: "Matthew T. O'Connor" User-Agent: Thunderbird 1.4 (Windows/20050908) MIME-Version: 1.0 To: "Jim C. Nasby" CC: Gourish Singbal , "pgsql-admin@postgresql.org" Subject: Re: auto vacuuming References: <674d1f8a0603290206u55f114e1y7bfc2f83696fbada@mail.gmail.com> <20060331174802.GS49405@pervasive.com> <20060331185037.GF14204@surnet.cl> <442DA0CA.1050901@zeut.net> <20060331224733.GX49405@pervasive.com> In-Reply-To: <20060331224733.GX49405@pervasive.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.126 required=5 tests=[AWL=0.126] X-Spam-Score: 0.126 X-Spam-Level: X-Archive-Number: 200603/409 X-Sequence-Number: 21166 >> I think the closest approximation of disabling autovacuum on a per >> database basis is to connect to the database in question and perform: >> >> update pg_autovacuum set enabled = 'false'; >> >> This will prevent autovacuum from vacuuming or analyzing any of the >> tables in the database, but will still check for XID wraparound. >> > > Problem with that is any time you add a table you'd need to re-run that > command. Wouldn't be so bad if we had DDL triggers, but... > Probably a dumb comment, but can you set a default value for the enabled column?