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 B011611F68E5 for ; Fri, 31 Mar 2006 23:29:04 -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 56586-05 for ; Fri, 31 Mar 2006 23:29:04 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 0BADB11F68E2 for ; Fri, 31 Mar 2006 23:29:01 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k313T1SV006992; Fri, 31 Mar 2006 22:29:01 -0500 (EST) To: "Matthew T. O'Connor" cc: "Jim C. Nasby" , Gourish Singbal , "pgsql-admin@postgresql.org" Subject: Re: auto vacuuming In-reply-to: <442DA0CA.1050901@zeut.net> References: <674d1f8a0603290206u55f114e1y7bfc2f83696fbada@mail.gmail.com> <20060331174802.GS49405@pervasive.com> <20060331185037.GF14204@surnet.cl> <442DA0CA.1050901@zeut.net> Comments: In-reply-to "Matthew T. O'Connor" message dated "Fri, 31 Mar 2006 16:36:10 -0500" Date: Fri, 31 Mar 2006 22:29:01 -0500 Message-ID: <6991.1143862141@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.114 required=5 tests=[AWL=0.114] X-Spam-Score: 0.114 X-Spam-Level: X-Archive-Number: 200603/411 X-Sequence-Number: 21168 "Matthew T. O'Connor" writes: > 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'; Not really gonna help unless you insert a row into pg_autovacuum for each table in the database. As I just commented in another reply, I don't actually believe in the value of disabling autovac entirely --- it should at least be able to fire when you are risking XID wraparound. What could make sense is to push the thresholds up to very large values, such that autovac won't fire until you've forgotten manual vacuums for a very long time. And that you can already do on a per-database basis, using ALTER DATABASE SET. (Or at least, it *should* work to do that; if the autovac process fails to absorb per-db values for its GUC variables, then we ought to fix it. I'm too lazy to test it right now...) regards, tom lane