id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc 1472,Disabling SEQSCAN is now a *bad* idea.,warmerdam,Mateusz Łoskot,"{{{ Found it. There's a bug in OGR, which dates back to 2001, when it wasn't a bug, it was a feature. hResult = PQexec(hPGConn, ""SET ENABLE_SEQSCAN = OFF""); Frank us turning off sequence scanning as part of his query setup. This is fine if you are only pulling a few features from the table, but if you are pulling *all* the features, it is brutally inefficient. In the new ""Modern Era"" (since PostGIS 0.8, really) PostGIS is correctly integrated into the query planner, so PostgreSQL will use the indexes when ""needed"" and not otherwise. Back when Frank wrote this, PostgreSQL would ignore the spatial indexes unless you forced it not to, which was desirable most of the time, so he forced it to use the indexes. Paul }}}",defect,closed,high,,OGR_SF,1.4.0,major,fixed,,