(cost=17214.16..17276.20 rows=6204 width=254) (actual
time=866317.923..866320.316 rows=7612 loops=1)
-> CTE Scan on rast_select r (cost=0.00..1240.66 rows=62033
width=254) (actual time=257.625..863555.082 rows=7677 loops=1)
Total runtime: 866691.113 ms
On Fri, May 29, 2015 at 6:40 AM, PT
n on poly s (cost=0.00..62.18 rows=3109 width=250)
On Wed, May 27, 2015 at 4:31 PM, PT wrote:
> On Tue, 26 May 2015 12:52:24 -0500
> David Haynes II wrote:
>
> > Hello,
> >
> > I have a question about the query optimizer and its performance on
> spatial
> >
Hello,
I have a question about the query optimizer and its performance on spatial
datasets, specifically rasters. My use case is rather unique, the
application that I am developing allows users to request summarizations of
various geographic boundaries around the world. Therefore our raster
datase
