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 08A4511F6235 for ; Fri, 31 Mar 2006 23:32:47 -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 58794-01 for ; Fri, 31 Mar 2006 23:32:46 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from projects.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id A9A3511F6222 for ; Fri, 31 Mar 2006 23:32:44 -0400 (AST) Received: from [192.168.15.100] (or-67-76-146-141.sta.sprint-hsd.net [67.76.146.141]) (authenticated bits=0) by projects.commandprompt.com (8.13.4/8.13.4) with ESMTP id k313WjPl001928; Fri, 31 Mar 2006 19:32:45 -0800 Message-ID: <442DF45E.4090409@commandprompt.com> Date: Fri, 31 Mar 2006 19:32:46 -0800 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Mail/News 1.5 (X11/20060309) MIME-Version: 1.0 To: Tom Lane CC: Alvaro Herrera , "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> <6933.1143861467@sss.pgh.pa.us> In-Reply-To: <6933.1143861467@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (projects.commandprompt.com [192.168.2.159]); Fri, 31 Mar 2006 19:32:46 -0800 (PST) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.092 required=5 tests=[AWL=0.092] X-Spam-Score: 0.092 X-Spam-Level: X-Archive-Number: 200603/412 X-Sequence-Number: 21169 > > 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. Sure.. a database that has over 2500 connections per a directly connected Java rich client... I don't want autovac running on it from 8-8 but after that I will run my own vacuum process. I am smart enough to manage my data. If I want autovac I will turn it on. Joshua D. Drake > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/