Received: from sss.pgh.pa.us ([216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3GNnQu13989 for ; Mon, 16 Apr 2001 19:49:26 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f3GNn6R19852; Mon, 16 Apr 2001 19:49:06 -0400 (EDT) To: Jeff Hoffmann cc: Julian Scarfe , pgsql-sql@postgresql.org Subject: Re: RTREE on points In-reply-to: <3ADB65F4.6F83A1E7@propertykey.com> References: <9bbtqv$688$1@news.tht.net> <3ADAFF38.E7147C8D@propertykey.com> <008f01c0c68a$b6651c00$2285fd3e@julian> <3ADB65F4.6F83A1E7@propertykey.com> Comments: In-reply-to Jeff Hoffmann message dated "Mon, 16 Apr 2001 16:36:52 -0500" Date: Mon, 16 Apr 2001 19:49:06 -0400 Message-ID: <19849.987464946@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200104/258 X-Sequence-Number: 2608 Jeff Hoffmann writes: > yes, it does seem like a little more work, but there doesn't seem to be > a lot of usage of the geometric functions by the developers to look at > missing features -- they're mostly just reactive to problems. Jeff's correct, none of the core developers have much time to spend on adding features to the geometric datatypes. If someone else wants to step up to the plate, though, contributions are welcome ;-) The procedure for adding a new index opclass is somewhat documented for btree opclasses. To add an rtree opclass you'd be adding a different set of operators and support functions, which set isn't documented anywhere that I know of; you'd have to look at the existing examples to figure out what is needed. BTW, you should also look at the GIST stuff and figure out whether it might not be better to develop a GIST opclass instead of rtree. In the long run I suspect GIST will be better supported than rtree, since it's more general. regards, tom lane