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 2A0B511F6C2A for ; Fri, 31 Mar 2006 23:17:52 -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 56909-01 for ; Fri, 31 Mar 2006 23:17:52 -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 9DDC711F6C26 for ; Fri, 31 Mar 2006 23:17:49 -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 k313HloZ006934; Fri, 31 Mar 2006 22:17:47 -0500 (EST) To: Alvaro Herrera cc: "Jim C. Nasby" , Gourish Singbal , "pgsql-admin@postgresql.org" Subject: Re: auto vacuuming In-reply-to: <20060331185037.GF14204@surnet.cl> References: <674d1f8a0603290206u55f114e1y7bfc2f83696fbada@mail.gmail.com> <20060331174802.GS49405@pervasive.com> <20060331185037.GF14204@surnet.cl> Comments: In-reply-to Alvaro Herrera message dated "Fri, 31 Mar 2006 14:50:37 -0400" Date: Fri, 31 Mar 2006 22:17:47 -0500 Message-ID: <6933.1143861467@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/410 X-Sequence-Number: 21167 Alvaro Herrera writes: > Jim C. Nasby wrote: >> 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. I can't think of one either. Real question is, why would you want to? Disabled autovac would for instance be unable to protect you against XID wraparound, which IMHO is one of the major advantages of running it at all. The handwriting on the wall says that autovac will soon be on by default, and perhaps become not-disablable some day after that (like the second or third time we hear from someone who's lost their data to XID wraparound after disabling it). So if there's a really convincing use-case for locking autovac out of specific databases, we'd better hear it soon. regards, tom lane