From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruno Wolff III <bruno@wolff.to>
Cc: Sean Davis <sdavis2@mail.nih.gov>
Cc: pgsql-sql@postgresql.org
Subject: Re: R-tree and start/end queries
Date: Wed, 21 Sep 2005 15:43:14 -0400
Message-ID: <20223.1127331794@sss.pgh.pa.us> (raw)
In-Reply-To: <20050921183837.GA27439@wolff.to>
References: <BF571628.EF19%sdavis2@mail.nih.gov>
<20050921183837.GA27439@wolff.to>
Bruno Wolff III <bruno@wolff.to> writes:
> There is a built in type for line segments that uses floating point. That
> will probably be usable by you directly unless the integers can can large
> enough that precision is a problem. There is an overlaps operator for the
> geometric types that could be used to answer your sample questions.
However, there's no built-in rtree opclass for that datatype, so he'd
still be stuck with respect to getting indexing support for overlaps
queries.
I think the contrib/seg datatype might help, though the precision issue
is still a possible problem.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruno@wolff.to, sdavis2@mail.nih.gov
Subject: Re: R-tree and start/end queries
In-Reply-To: <20223.1127331794@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox