[postgis-devel] [PostGIS] #1506: [raster] ST_Quantile('rastertable' ...) segfault and is missing in documentation

[PostGIS]

#1506: [raster] ST_Quantile('rastertable' ...)  segfault and is missing in
documentation
-----------------------------+----------------------------------------------
  Reporter:  joanw           |       Owner:  dustymugs    
      Type:  defect          |      Status:  closed       
  Priority:  blocker         |   Milestone:  PostGIS 2.0.0
 Component:  postgis raster  |     Version:  2.0.x        
Resolution:  fixed           |    Keywords:               
-----------------------------+----------------------------------------------

Comment(by pracine):

 In this case you set the flag to false even if what you are setting is
 only nodata and you loose the optimization. You can ST_Rescan() all the
 rasters to reset the flag once a week if you do a lot of edit (like a SQL
 VACUUM). This is ONLY if you edit the rasters, which is a fraction of the
 applications. Other application always get the optimization. This is what
 I discussed with Jorge.

 A lot of code and changes for not much optimization for coverages having
 at least one tile complete with nodata which are not all of them... Really
 a low priority.

 I'm glad that this argument discard the idea of having empty tiles when
 only filled with nodata. You would also have to check for every edited
 pixel in order to determine if the resulting tile is all nodata to make it
 empty...

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/1506#comment:9>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.