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

[Mateusz Łoskot]

On 7 December 2011 18:13, dustymugs <dustymugs at gmail.com> wrote:
> On 12/07/2011 09:49 AM, Mateusz Łoskot wrote:
>>
>> If I may, I'd like to gently complain about the recent change in the
>> raster part:
>>
>> http://trac.osgeo.org/postgis/changeset/8313
>>
>> Do we really want this change?
>> In my opinion, it is not a good idea for the best performance possible.
>>
>> The natural block concept is there for purpose and operating on larger
>> strips performs better.
>>
>> I had a quick talk with Frank and, I hope Frank does not mind me quoting
>> him, there is another issue:
>>
>> "It was my understanding/hope that postgis raster would be highlyoptimized
>> for the postgis regular blocking case and I had hoped that in at least
>> some cases that would be setup to map 1:1 to regular blocking in source
>> or destination GDAL files.
>> This certainly discards any hope of such optimization in this api."
>
>
> I made this change because of an issue I was experiencing using "natural"
> blocks and specific rasters in the rt_resample regression test.  Though the
> "natural" blocks worked perfectly fine in every other regression test, I had
> two rasters in rt_resample that would fail.  This can be seen using r8309
> and raster 1.15 in the rt_resample regression test.

Bborie,

Understood.
I'm not having any working development environment for PostGIS now.
I hope to bring it back within next weeks, then I will be able to take
a look myself.
Thus, I'm not asking for any revert or fix action.
I just wanted to point this, so it doesn't sneak unattended and it can
be addressed in near future with some solution.
I understand it is implementation detail, so there is no problem to get
back to natural blocks without changing the SQL interface.

Perhaps I should have submitted a ticket.

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net