Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 0D8369FB713 for ; Tue, 16 Oct 2007 19:04:25 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 52784-06 for ; Tue, 16 Oct 2007 19:04:15 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from vms044pub.verizon.net (vms044pub.verizon.net [206.46.252.44]) by postgresql.org (Postfix) with ESMTP id 0ED0B9FB6ED for ; Tue, 16 Oct 2007 19:04:19 -0300 (ADT) Received: from new-host.home ([71.179.23.138]) by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JQ000MO3YLBSLW1@vms044.mailsrvcs.net> for pgsql-docs@postgresql.org; Tue, 16 Oct 2007 17:03:15 -0500 (CDT) Date: Tue, 16 Oct 2007 18:02:53 -0400 From: Robert Treat Subject: Re: FAQ corrections In-reply-to: <200710161946.l9GJk6b06643@momjian.us> To: Bruce Momjian Cc: pgsql-docs@postgresql.org, Ian Barwick Message-id: <200710161802.54084.xzilla@users.sourceforge.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <200710161946.l9GJk6b06643@momjian.us> User-Agent: KMail/1.9.1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/62 X-Sequence-Number: 4483 On Tuesday 16 October 2007 15:46, Bruce Momjian wrote: > Robert Treat wrote: > > On Friday 12 October 2007 14:04, Ian Barwick wrote: > > > Hi > > > > > > attached some minor corrections, mainly completion of removal of > > > the "relation with OID ##### does not exist" item, and some URL > > > corrections. > > > > I'm curious why this was removed. We still get this question a bit on irc > > and there aren't any more appropriate answers for any released version > > than what the FAQ contained... > > The FAQ will match the release it goes with or we could just delay its > removal until after 8.3 is in major circulation and say it only applies > to pre-8.3. I think it should remain, with an addition that this problem should be resolved as of PostgreSQL 8.3. Hard to say exactly when, but I would think it would be at least untill 8.3 is released, and probably better would be 6 months or so later, when (hopefully) people stop asking about this. IMHO. -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL