[postgis-devel] [raster] About recent commit r8313

[dustymugs]

On 12/07/2011 10:34 AM, Chris Hodgson wrote:
> Thanks for the clarification Bborie. I must have misread (I wish I had
> more time to pay attention to what is going on with raster development)
> but I thought I had read that, because of the lack of information about
> regular blocking (no constraint to check) it was going to be tossed.
> Sorry for the noise.
>
> However, given that, it would be still nice to be able to work with the
> gdal blocking concept for best performance. Perhaps that will have to
> wait until there is time to sort out the problems you were having.
>

Yes, I would have liked to keep the "natural" gdal blocking.  But with 
the error I was experiencing and the non-ideal solutions to get around 
the error, I went with what I felt was safest with the least number of 
loops/evaluations.

I still need to test and see if the error occurs if I use GDAL 1.6, 1.7, 
and 1.8.

-bborie