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 511EB11F7515 for ; Mon, 3 Apr 2006 00:05:43 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 09043-01 for ; Mon, 3 Apr 2006 00:05:41 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mx2.surnet.cl (mx2.surnet.cl [216.155.73.181]) by postgresql.org (Postfix) with ESMTP id 8B57311F74AF for ; Mon, 3 Apr 2006 00:05:40 -0300 (ADT) Received: from unknown (HELO cluster.surnet.cl) ([216.155.73.165]) by mx2.surnet.cl with ESMTP; 02 Apr 2006 23:05:37 -0400 X-IronPort-AV: i="4.02,198,1139194800"; d="scan'208"; a="40350305:sNHT19303796" Received: from alvh.no-ip.org (201.220.123.23) by cluster.surnet.cl (7.0.043) (authenticated as alvherre@surnet.cl) id 43A978FD00D1A8A1; Sun, 2 Apr 2006 23:05:36 -0400 Received: by alvh.no-ip.org (Postfix, from userid 1000) id 6719EC2DC4F; Sun, 2 Apr 2006 23:05:36 -0400 (CLT) Date: Sun, 2 Apr 2006 23:05:36 -0400 From: Alvaro Herrera To: Tom Lane Cc: "Jim C. Nasby" , Gourish Singbal , "pgsql-admin@postgresql.org" Subject: Re: auto vacuuming Message-ID: <20060403030536.GA6701@surnet.cl> Mail-Followup-To: Tom Lane , "Jim C. Nasby" , Gourish Singbal , "pgsql-admin@postgresql.org" References: <674d1f8a0603290206u55f114e1y7bfc2f83696fbada@mail.gmail.com> <20060331174802.GS49405@pervasive.com> <20060331185037.GF14204@surnet.cl> <6933.1143861467@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6933.1143861467@sss.pgh.pa.us> User-Agent: Mutt/1.5.11+cvs20060126 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.734 required=5 tests=[AWL=0.734] X-Spam-Score: 0.734 X-Spam-Level: X-Archive-Number: 200604/24 X-Sequence-Number: 21193 Tom Lane wrote: > 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). I don't think we will see much people losing data to Xid wraparound anymore, now that the server refuses to work when the wraparound is imminent. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support