Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id DC7499FBA30; Mon, 14 May 2007 23:49:09 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 14525-01; Mon, 14 May 2007 23:49:07 -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 90B609FB9F6; Mon, 14 May 2007 23:49:06 -0300 (ADT) Received: from localhost (mailbox.samurai.com [205.207.28.82]) by mailbox.samurai.com (Postfix) with ESMTP id 34AD561D29; Mon, 14 May 2007 22:49:05 -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 ibXkES29uhLE; Mon, 14 May 2007 22:49:03 -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 721FC61D2D; Mon, 14 May 2007 22:49:03 -0400 (EDT) Subject: Re: [PATCHES] Autovacuum and XID wraparound From: Neil Conway To: Bruce Momjian Cc: David Fetter , Tom Lane , PostgreSQL Docs , PostgreSQL Patches In-Reply-To: <200705142022.l4EKMNq20973@momjian.us> References: <200705142022.l4EKMNq20973@momjian.us> Content-Type: text/plain Date: Mon, 14 May 2007 22:49:03 -0400 Message-Id: <1179197343.6047.47.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/38 X-Sequence-Number: 4267 On Mon, 2007-14-05 at 16:22 -0400, Bruce Momjian wrote: > I agree with Tom. I don't think the current behavior is a major issue > for users for it to be mentioned more than it already is Are you really suggesting that we shouldn't modify config.sgml to note that "autovacuum = off" does not actually imply that "the autovacuum daemon is disabled"? ISTM that plainly violates the principle of least surprise -- it is almost the definition of what an entry in config.sgml *should* include. > though if you want to move one of those, we can do that. So the change would be okay if we also removed one of the other mentions in an unrelated section of the manual? I don't see the logic. -Neil