Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: R-tree and start/end queries
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Bruno Wolff III <bruno(at)wolff(dot)to>
- Cc: Sean Davis <sdavis2(at)mail(dot)nih(dot)gov>, pgsql-sql(at)postgresql(dot)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> <text/plain>
Bruno Wolff III <bruno(at)wolff(dot)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
- References:
- R-tree and start/end queries
- From: Sean Davis
- Re: R-tree and start/end queries
- From: Bruno Wolff III
- R-tree and start/end queries
- Prev by Date: Re: R-tree and start/end queries
- Next by Date: delete item[5] from varchar[] array???
- Previous by thread: Re: R-tree and start/end queries
- Next by thread: Re: R-tree and start/end queries
- Indexes: