[postgis-devel] ST_Value performance

[Pierre Racine]

I better see your point now. Must be the update itself that takes long, not the ST_Value().

Try just a SELECT ST_Value()

> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net [mailto:postgis-devel-
> bounces at postgis.refractions.net] On Behalf Of Sandro Santilli
> Sent: Tuesday, January 31, 2012 2:48 PM
> To: PostGIS Development Discussion
> Subject: Re: [postgis-devel] ST_Value performance
> 
> On Tue, Jan 31, 2012 at 02:44:41PM -0500, Pierre Racine wrote:
> > > Now I'm running an update adding the value to each of those rows,
> > > using ST_Value. I do understand that over 200k calls are a lot to
> > > do, but fetching a value itself shouldn't take long, right ?
> > > It's a 661x313 pixels raster.
> >
> > Is 40 minutes for deserializing 200000 times that raster too much? You tell
> me...
> 
> The same raster deserialized 200000 times for ST_PixelAsPolygon as well, but
> didn't take so much.
> 
> --strk;
> 
>   ,------o-.
>   |   __/  |    Thank you for PostGIS-2.0 Topology !
>   |  / 2.0 |    http://www.pledgebank.com/postgistopology
>   `-o------'
> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel