[postgis-devel] Re: [postgis-users] create tables smarter

[David William Bitner]

I'm not actually doing this, but I helped someone else on IRC set this up a
while ago because the overlaps operator for time does not make use of any
indexes on time data types.  The solution that he used was to create 1-d
lines (ie 0 1,0 5) that represented a time period so he could just use &&
for an indexed overlaps operator.  A little hacky, but it seemed to work
quite well for him.

On Fri, Jun 6, 2008 at 9:33 AM, Mark Cave-Ayland <
mark.cave-ayland at siriusit.co.uk> wrote:

> David William Bitner wrote:
>
>> One use in adding 1-dimension support would be to make it easier for folks
>> who are using postgis for non-spatial utility for using the GIST indexing.
>> For example there are some people throwing time as a unix epoch into
>> PostGIS
>> in order to do efficient time period overlaps queries.
>>
>
> Errr... this may be a silly question, but why are they not using
> PostgreSQL's in-built (and more recently GiST-based) R-Tree index if they
> are indexing non-geometry fields in this way?
>
>
>
> ATB,
>
> Mark.
>
> --
> Mark Cave-Ayland
> Sirius Corporation - The Open Source Experts
> http://www.siriusit.co.uk
> T: +44 870 608 0063
>



-- 
************************************
David William Bitner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20080606/1d787616/attachment.html>