[postgis-users] Slow Query Times for Split Tiles

[Pierre Racine]

I think 2 minutes for 50x50 tiles is reasonable. If you want faster results reload your raster tiling it 10x10 using the -k option.

> -----Original Message-----
> From: postgis-users-bounces at postgis.refractions.net [mailto:postgis-users-
> bounces at postgis.refractions.net] On Behalf Of elliott
> Sent: Friday, November 04, 2011 8:50 AM
> To: PostGIS Users Discussion
> Subject: Re: [postgis-users] Slow Query Times for Split Tiles
> 
> Yes, I am certain that the table has been indexed. If I use the raster2pgsql.py
> script with the -I option to load additional data, it complains that the table is
> already indexed.
> 
>   Querying for 10,000 lat/lons on locations that have not been imported
> into the database is very fast returning in 2 seconds.   It can very
> quickly determine that there are no intersections.  However, when there are
> intersections for all 10,000 lat/lons, the query is taking over 2 minutes.  Would
> you expect the performance to be better than that?
> 
> On 11/3/2011 4:32 PM, Pierre Racine wrote:
> >> Thanks for the suggestion.  From the output, it doesn't look like it
> >> is using the index even though an index was created with the
> >> raster2pgsql.py script.  Is there a specific way to tell the query to use the
> index?
> >>
> > Could you make sure you really created an index on the 50x50 pixel table. I
> don't see the -I option in your raster2pgsql.py command...
> >
> > Pierre
> > _______________________________________________
> > postgis-users mailing list
> > postgis-users at postgis.refractions.net
> > http://postgis.refractions.net/mailman/listinfo/postgis-users
> >
> >
> 
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users