[postgis-devel] [PostGIS] #1504: Segfault running ST_EstimatedExtent()

[PostGIS]

#1504: Segfault running ST_EstimatedExtent()
-------------------------+--------------------------------------------------
  Reporter:  brushtyler  |       Owner:  pramsey      
      Type:  defect      |      Status:  reopened     
  Priority:  blocker     |   Milestone:  PostGIS 2.0.0
 Component:  postgis     |     Version:  trunk        
Resolution:              |    Keywords:               
-------------------------+--------------------------------------------------
Changes (by brushtyler):

  * status:  closed => reopened
  * resolution:  invalid =>


Comment:

 I've found a way to reproduce it:

 {{{
 test=> CREATE TABLE "test_1504" (id int PRIMARY KEY, geom
 geometry(LineString,3003));
 NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
 "test_1504_pkey" for table "test_1504"
 CREATE TABLE
 test=> INSERT INTO "test_1504" (id, geom) VALUES (0, NULL);
 INSERT 0 1
 test=> ALTER TABLE "test_1504" ALTER COLUMN geom TYPE geometry(LineString,
 -1);
 NOTICE:  SRID value -1 converted to the officially unknown SRID value 0
 NOTICE:  SRID value -1 converted to the officially unknown SRID value 0
 ALTER TABLE
 test=> select st_estimated_extent('test_1504', 'geom');
 The connection to the server was lost. Attempting reset: Failed.
 }}}

 NB: I tried to add with a geometry not NULL, but I got the same result
 (segfault).

 After reconnecting and querying the table to get srid it returns a strange
 result:
 {{{
 test=> select st_srid(geom) from "test_1504";
  st_srid
 ---------

 (1 row)
 }}}

 I think that pg_dump now returns that strange (and maybe random) srid >
 MAX_SRID.

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