[postgis-tickets] [PostGIS] #5277: PG16 crashing on raster install

[PostGIS]

#5277: PG16 crashing on raster install
---------------------+---------------------------
 Reporter:  robe     |      Owner:  robe
     Type:  defect   |     Status:  new
 Priority:  blocker  |  Milestone:  PostGIS 3.4.0
Component:  raster   |    Version:  master
 Keywords:           |
---------------------+---------------------------
 I thought it was just my setup, but debbie is having the same issue with
 her PG16 run as I am


 {{{
 22:54:44  topology has been added to end of database search_path
 22:54:44 (1 row)
 22:54:44
 22:54:44 NOTICE:  schema "public" already exists, skipping
 22:54:44 NOTICE:  schema "public" already exists, skipping
 22:54:44 psql:/var/lib/jenkins/workspace/postgis/branches/3.4/regress/00
 -regress-install/share/contrib/postgis/rtpostgis.sql:111: server closed
 the connection unexpectedly
 22:54:44        This probably means the server terminated abnormally
 22:54:44        before or while processing the request.
 22:54:44 psql:/var/lib/jenkins/workspace/postgis/branches/3.4/regress/00
 -regress-install/share/contrib/postgis/rtpostgis.sql:111: error:
 connection to server was lost
 22:54:44
 -----------------------------------------------------------------------------
 22:54:44 make: *** [regress/runtest.mk:24: check-regress] Error 1
 22:54:44 Build step 'Execute shell' marked build as failure
 22:54:44 Triggering a new build of PostgreSQL stop
 22:54:44 Finished: FAILURE
 }}}

 It just crashes.  ON mine it crashes on line 100 of rtpostgis.sql

 As best I can tell, this started happening with the commit of


 https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=a73952b795632b2cf5acada8476e7cf75857e9be

 I haven't checked to see what that line corresponds to yet.
 {{{
 Commit a73952b795632b2cf5acada8476e7cf75857e9be by michael

 Add check on initial and boot values when loading GUCs

 This commit adds a function to perform a cross-check between the initial
 value of the C declaration associated to a GUC and its actual boot
 value in assert-enabled builds.  The purpose of this is to prevent
 anybody reading these C declarations from being fooled by mismatched
 values before they are loaded at program startup.

 The following rules apply depending on the GUC type:
 * bool - can be false, or same as boot_val.
 * int - can be 0, or same as the boot_val.
 * real - can be 0.0, or same as the boot_val.
 * string - can be NULL, or strcmp'd equal to the boot_val.
 * enum - equal to the boot_val.

 This is done for the system as well custom GUCs loaded by external
 modules, which may require extension developers to adapt the C
 declaration of the variables used by these GUCs (testing this change
 with some of my own modules has allowed me to catch some stupid typos,
 FWIW).  This may finish by being a bad experiment depending on the
 feedbcak received, but let's see how it goes.

 Author: Peter Smith
 Reviewed-by: Nathan Bossart, Tom Lane, Michael Paquier, Justin Pryzby
 Discussion:
 https://postgr.es/m/CAHut+PtHE0XSfjjRQ6D4v7+dqzCw=d+1a64ujra4EX8aoc_Z+w@mail.gmail.com
 }}}


 On my setup lines 95 - 107 are these and it is crashing at 100


 {{{
 -- part of Raster type
 -- expects input to be Hex WKB
 CREATE OR REPLACE FUNCTION raster_in(cstring)
     RETURNS raster
     AS 'C:/ming64gcc81/projects/postgis/postgis-git/regress/00-regress-
 install/lib/postgis_raster-3.4','RASTER_in'
     LANGUAGE 'c' IMMUTABLE STRICT PARALLEL SAFE;
 # line 100
 -- part of Raster type
 -- expects output to be Hex WKB
 CREATE OR REPLACE FUNCTION raster_out(raster)
     RETURNS cstring
     AS 'C:/ming64gcc81/projects/postgis/postgis-git/regress/00-regress-
 install/lib/postgis_raster-3.4','RASTER_out'
     LANGUAGE 'c' IMMUTABLE STRICT PARALLEL SAFE;
 }}}
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/5277>
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.