Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id AEFF89FB95C; Mon, 14 May 2007 01:34:35 -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 40522-02; Mon, 14 May 2007 01:34:30 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mailbox.samurai.com (mailbox.samurai.com [205.207.28.82]) by postgresql.org (Postfix) with ESMTP id 8630A9FB967; Mon, 14 May 2007 01:34:31 -0300 (ADT) Received: from localhost (mailbox.samurai.com [205.207.28.82]) by mailbox.samurai.com (Postfix) with ESMTP id E881F61D11; Mon, 14 May 2007 00:34:30 -0400 (EDT) X-Virus-Scanned: by amavisd-new at mailbox.samurai.com Received: from mailbox.samurai.com ([205.207.28.82]) by localhost (mailbox.samurai.com [205.207.28.82]) (amavisd-new, port 10024) with LMTP id eyxoFgHyP7oo; Mon, 14 May 2007 00:34:29 -0400 (EDT) Received: from [192.168.0.101] (CPE3285f62f0d42-CM0011aec5ebbc.cpe.net.cable.rogers.com [74.103.69.144]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mailbox.samurai.com (Postfix) with ESMTP id 8B7E461D0D; Mon, 14 May 2007 00:34:29 -0400 (EDT) Subject: Re: [PATCHES] Autovacuum and XID wraparound From: Neil Conway To: Tom Lane Cc: David Fetter , PostgreSQL Docs , PostgreSQL Patches In-Reply-To: <23394.1179108400@sss.pgh.pa.us> References: <20070514011740.GH14860@fetter.org> <23394.1179108400@sss.pgh.pa.us> Content-Type: text/plain Date: Mon, 14 May 2007 00:34:29 -0400 Message-Id: <1179117269.6047.3.camel@goldbach> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/27 X-Sequence-Number: 4256 On Sun, 2007-13-05 at 22:06 -0400, Tom Lane wrote: > This fact is already documented in at least three places; do we really > need two more? I think we need to at least modify the documentation for the autovacuum GUC parameter, which currently states only that it "controls whether the server should run the autovacuum launcher daemon" -- this is not strictly true, and in any case, it isn't the whole story. > The proposed addition to postgresql.conf seems particularly > over-the-top I agree that this information doesn't really belong in postgresql.conf. -Neil