Re: geometry poligons performance and index - Mailing list pgsql-admin

From Peter Koczan
Subject Re: geometry poligons performance and index
Date
Msg-id 4544e0330709041958o3bd58974gf39f64ae083c81d6@mail.gmail.com
Whole thread Raw
In response to geometry poligons performance and index  (giuseppe.derossi@email.it)
List pgsql-admin
>  The results are ok, but the query is too slow. I tried to applay a GIST and
>  gtree index but performance did not improve.
>  By explaining the query I see that the where condition gets the query slow.
>  Is there a more simple way to check if two poligons have a not null
>  intersection (they overlap)?
>
>  Is there a kind of index I can use ?

If you stored the polygon geometries in the same table, you could use
a functional index (give the CREATE INDEX statement a function to
evaluate rather than a column). Check the CREATE INDEX page for
caveats. Beware that the index would grow with the square of the
number of rows if you did it like this.

Peter

pgsql-admin by date:

Previous
From: "Tena Sakai"
Date:
Subject: Re: default port number
Next
From: Daniel Rubio
Date:
Subject: Can't login to 8.2.4 if not superuser...