[postgis-tickets] [PostGIS] #2359: raster2pgsql - large collection of examples of different bugs in -l (overviews)

PostGIS trac at osgeo.org
Thu Jun 13 10:26:40 PDT 2013


#2359: raster2pgsql - large collection of examples of different bugs in -l
(overviews)
---------------------+------------------------------------------------------
  Reporter:  gbell   |       Owner:  dustymugs             
      Type:  defect  |      Status:  reopened              
  Priority:  medium  |   Milestone:  PostGIS 2.0.4         
 Component:  raster  |     Version:  2.0.x                 
Resolution:          |    Keywords:  raster2pgsql overviews
---------------------+------------------------------------------------------
Changes (by gbell):

  * priority:  high => medium
  * status:  closed => reopened
  * resolution:  fixed =>


Comment:

 Hi,

 Thank you for investigating so thoroughly, great work!
 Interesting that so many different variations of error output originate in
 a single bug.

 Item 7. I have retested. This bug is real and distinct. Can we leave this
 bug report open until someone else can attempt to reproduce it?

 raster2pgsql -t 100x100 -I -C -M ilatlon_float.tif -Y -l 4 temp.test |
 psql sl
 raster2pgsql -t 100x100 -I -C -M ilatlon_float.tif -Y -l 4 temp.test |
 psql sl

 This produces the error for me. It isn't produced when -l4 is missing; it
 isn't produced with bogota.tif (it can't generate overviews). The stack
 trace is huge.

 glibc is glibc-2.16-28.fc18.x86_64

 Perhaps the bug is being exposed (or being caused) by the glibc version.


 Item 0c.

 "raster2pgsql never connects (and can't connect) to the database so it has
 no idea if the table already exists."

 This statement is true, but I think it is not important to solving this
 problem.

 Is there anything to prevent raster2pgsql from emitting SQL that checks if
 the named table already exists when it is run, and aborts cleanly if it
 does exist, with an appropriate message to the user / SQL console?

 I would recommend that as a future improvement. I'm reopening for this in
 particular.

 Again, thank you for your time in investigating.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2359#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