Path: news.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!newsfeed-east.nntpserver.com!nntpserver.com!news-out.visi.com!hermes.visi.com!news1.optus.net.au!optus!spool01.syd.optusnet.com.au!spool.optusnet.com.au!not-for-mail Newsgroups: comp.databases.oracle.server Subject: Re: index rebuilding... From: Noons References: <3EXZ9.53855$GX4.2199677@news2.east.cox.net> <3E39A86C.3143C919@exesolutions.com> <69f6c1c8.0301301921.143657e6@posting.google.com> <998d28f7.0301310721.3c724ec@posting.google.com> <3E3AAC94.B8B6073C@exesolutions.com> <6By_9.37587$jM5.94689@newsfeeds.bigpond.com> Organization: Completely disorganized, but still kicking! Message-ID: User-Agent: Xnews/L5 Date: 02 Feb 2003 10:08:31 GMT Lines: 30 NNTP-Posting-Host: 211.28.171.43 X-Trace: 1044180511 27993 211.28.171.43 Xref: newsfeed1.easynews.com comp.databases.oracle.server:174503 X-Received-Date: Sun, 02 Feb 2003 03:09:40 MST (news.easynews.com) "Jonathan Lewis" wrote in news:b1ipul$gtj$1$8300dec7@news.demon.co.uk and I quote: > > Of course, this does mean that Oracle doesn't > use B*Trees, as it's manuals have claimed since > at least 5.1 - it uses a version of B+trees. Akshally, the whole thing is terminally confusing. According to Knuth, B+trees and B*trees are quite different. And Oracle doesn't help with their "modified algorithm" B+trees thing. It all adds to the confusion. I'd bet if someone spends some time going through the actual index handling source code, it will come out that the algorithm is neither one nor the other and is in fact quite unique. It's one of the few areas where makers can still have some significant implementation differences, and of course distinguishing factors. The only reason we don't see the marketing dingbats pouring all over it is that the whole thing is arcane, to put it very mildly. -- Cheers Nuno Souto nsouto@optusnet.com.au.nospam