X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 3C7555E46CD for ; Tue, 31 Aug 2004 16:12:40 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 24347-08 for ; Tue, 31 Aug 2004 19:12:34 +0000 (GMT) Received: from window.monsterlabs.com (window.monsterlabs.com [216.183.105.176]) by svr1.postgresql.org (Postfix) with SMTP id D5CC45E4713 for ; Tue, 31 Aug 2004 16:12:32 -0300 (ADT) Received: (qmail 25209 invoked from network); 31 Aug 2004 19:12:32 -0000 Received: from w080.z064003242.bna-tn.dsl.cnc.net (HELO ?192.168.1.22?) (64.3.242.80) by 0 with SMTP; 31 Aug 2004 19:12:32 -0000 In-Reply-To: <200408311905.i7VJ5sv16159@candle.pha.pa.us> References: <200408311905.i7VJ5sv16159@candle.pha.pa.us> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: pgsql-docs@postgresql.org From: Thomas F.O'Connell Subject: Re: FAQ -- Index usage/speed Date: Tue, 31 Aug 2004 14:12:30 -0500 To: Bruce Momjian X-Mailer: Apple Mail (2.619) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/58 X-Sequence-Number: 2518 I thought about that, and it seems like the upgrade path from 7.x -> 8.x is going to be slower than among any of the 7.x releases. 8.0 is still several months away and it will probably be several months more before people who are affected by this issue in production databases. The other thing I thought about was a caveat in the 7.x documentation under indexes, as it doesn't seem to be mentioned anywhere. That would keep it off the general FAQ but let folks using 7.x releases know about it. -tfo On Aug 31, 2004, at 2:05 PM, Bruce Momjian wrote: > Yes, 4.8 would be the right spot. Not sure why we got so many reports > recently though. > > However, with this fixed in 8.0, it probably isn't worth adding to the > FAQ.