Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 156FD9FB626; Thu, 9 Aug 2007 05:30:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 65155-04; Thu, 9 Aug 2007 05:30:43 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from gauss.credativ.com (gauss.credativ.com [212.112.227.254]) by postgresql.org (Postfix) with ESMTP id 407BB9FB42D; Thu, 9 Aug 2007 05:30:17 -0300 (ADT) Received: from hawking.credativ.lan (exit.credativ.com [87.139.82.80]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gauss.credativ.com (Postfix) with ESMTP id 77173784B5; Thu, 9 Aug 2007 10:25:46 +0200 (CEST) From: Peter Eisentraut To: Decibel! Subject: Re: EnterpriseDB Postgres Date: Thu, 9 Aug 2007 10:30:12 +0200 User-Agent: KMail/1.9.5 Cc: pgsql-advocacy@postgresql.org, Dave Page , Joshua_Kramer References: <200708082338.19482.peter_e@gmx.net> <20070808214742.GU20424@nasby.net> In-Reply-To: <20070808214742.GU20424@nasby.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708091030.13110.peter_e@gmx.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/200 X-Sequence-Number: 11770 Am Mittwoch, 8. August 2007 23:47 schrieb Decibel!: > Well, you mentioned lack of vacuuming twice in your blog, so you're the > last person I expected to object to this. > > I don't see how leaving autovacuum turned off can be a good idea in a > package that's specifically meant to be easy. It's more of a general observation. Several downstream distributors turned autovacuum on by default some time ago, their decision process having been something like, "Automatic vacuum? Cool!". There are certainly cases where enabling autovacuum by default is reasonable. But remember the lengthy discussion we had before the 8.2 release about whether to turn it on, and the extensive development necessary for 8.3 to make enabling it by default safe. There was clearly more thought being put into it than some of the distributors did. -- Peter Eisentraut http://developer.postgresql.org/~petere/