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 D825411F6623 for ; Fri, 31 Mar 2006 17:35:51 -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 40495-10 for ; Fri, 31 Mar 2006 17:35:51 -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 D343B11F6613 for ; Fri, 31 Mar 2006 17:35:49 -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 1FPRHY-0000JX-SR; Fri, 31 Mar 2006 16:35:48 -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: <442DA0CA.1050901@zeut.net> Date: Fri, 31 Mar 2006 16:36:10 -0500 From: "Matthew T. O'Connor" User-Agent: Thunderbird 1.4 (Windows/20050908) MIME-Version: 1.0 To: "Jim C. Nasby" , Gourish Singbal , "pgsql-admin@postgresql.org" Subject: Re: auto vacuuming References: <674d1f8a0603290206u55f114e1y7bfc2f83696fbada@mail.gmail.com> <20060331174802.GS49405@pervasive.com> <20060331185037.GF14204@surnet.cl> In-Reply-To: <20060331185037.GF14204@surnet.cl> 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.127 required=5 tests=[AWL=0.127] X-Spam-Score: 0.127 X-Spam-Level: X-Archive-Number: 200603/406 X-Sequence-Number: 21163 Alvaro Herrera wrote: > Jim C. Nasby wrote: >> On Wed, Mar 29, 2006 at 03:36:36PM +0530, Gourish Singbal wrote: >>> we are using postgresql 8.1.3 and wanted to enable autovacuuming for only >>> one of the many databases on the same postgresql cluster. >>> pg_autovacuum seems to allow to ignore only a particular table and not the >>> database since column vacrelid is OID from pg_class table Are there any >>> suggestions to accomplish this tasks?. >> Currently there is no way to exclude entire databases from autovacuum. > > IIRC in one of the original patches I had added a way to do it. It was > rejected however; it was argued that there was another mechanism to > disable it. I don't remember what it was though. The only possibility > that comes to mind is "ALTER DATABASE SET autovacuum TO off" but I don't > see why would it work. 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. Matt