[postgis] Indexing....ack!

[harmonk00]

I have a table that contains about 90,000 rows.  Each row has a 
geometry column.  Each row has a 2D point as the value in that column.

The table looks something like this:

create table pole (bec_record_id numeric(8), ipid numeric(20), 
featuresymgeometries geometry);


SO...I then insert my 90,000 rows and THEN create the following index:

CREATE INDEX POLE_NDX_1 ON cable USING GIST ( featuresymgeometries 
GIST_GEOMETRY_OPS ) WITH ( ISLOSSY );


Then, I try the following select against the table:

explain select count(*) from  Pole where  Pole.featuresymgeometries 
&& 'BOX3D(-69.9392089498987 18.47719733442078,-69.9368322996733 
18.478711603947218)'::box3d

and I get this:

Aggregate  (cost=8699.73..8699.73 rows=1 width=0)
  ->  Seq Scan on pole  (cost=0.00..8677.16 rows=9025 width=0)


It did a full table scan...not good.

So then I turn the sequential scan stuff off:










To unsubscribe from this group, send an email to:
postgis-unsubscribe at yahoogroups.com

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/