[PostGIS] #5176: no data check in raster2pgsql and also ST_BandIsNoData are slow

PostGIS trac at osgeo.org
Wed Jun 24 12:54:27 PDT 2026


#5176: no data check in raster2pgsql and also ST_BandIsNoData are slow
---------------------+-----------------------------
  Reporter:  robe    |      Owner:  robe
      Type:  defect  |     Status:  new
  Priority:  medium  |  Milestone:  PostGIS Fund Me
 Component:  raster  |    Version:  master
Resolution:          |   Keywords:
---------------------+-----------------------------
Comment (by Darafei Praliaskouski <me@…>):

 In [changeset:"a4ecc46176c3fc0ab3fa69cf117d408bc622e592/git"
 a4ecc461/git]:
 {{{#!CommitTicketReference repository="git"
 revision="a4ecc46176c3fc0ab3fa69cf117d408bc622e592"
 doc: correct ST_BandIsNoData forceChecking default

 The SQL signature defaults forceChecking to false, and the function
 description already says the default is false. Align the synopsis so users
 looking for the cheap metadata path do not see the expensive forced scan
 advertised as the default.

 References #5176

 Closes https://github.com/postgis/postgis/pull/977
 }}}
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5176#comment:3>
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.


More information about the postgis-tickets mailing list