| 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: | 2005-09-21 19:43:14 |
| Message-ID: | 20223.1127331794@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew Peter | 2005-09-22 01:56:36 | delete item[5] from varchar[] array??? |
| Previous Message | Dmitri Bichko | 2005-09-21 19:29:34 | Re: R-tree and start/end queries |