[postgis-tickets] [PostGIS] #3822: Have postgis_full_version() also denote which version of PostgreSQL the scripts were built against

[PostGIS]

#3822: Have postgis_full_version() also denote which version of PostgreSQL the
scripts were built against
----------------------+---------------------------
  Reporter:  robe     |      Owner:  strk
      Type:  defect   |     Status:  reopened
  Priority:  medium   |  Milestone:  PostGIS 2.4.0
 Component:  postgis  |    Version:  2.3.x
Resolution:           |   Keywords:
----------------------+---------------------------
Changes (by robe):

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


Comment:

 strk I think this compare needs some work.

 I just did an


 {{{
 ALTER EXTENSION postgis UPDATE;
 }}}

 using winnie's built postgis 2.4.0beta4 tar ball for PostgreSQL 10.

 when I ran postgis_full_version();

 I got this:

 {{{
 POSTGIS="2.4.0beta1 r15614" PGSQL="100" (procs need upgrade for use with
 "PostgreSQL 10beta3 on x86_64-w64-mingw32, compiled by gcc.exe
 (x86_64-win32-seh-rev1, Built by MinGW-W64 project) 4.8.3, 64-bit")
 GEOS="3.7.0dev-CAPI-1.11.0 1618346" PROJ="Rel. 4.9.1, 04 March 2015"
 GDAL="GDAL 2.2.1, released 2017/06/23" LIBXML="2.7.8" LIBJSON="0.12"
 LIBPROTOBUF="1.2.1" RASTER

 }}}

 and I notice:


 {{{

 SELECT _postgis_pgsql_version();
 }}}

 returns


 {{{
 PostgreSQL 10beta3 on x86_64-w64-mingw32, compiled by gcc.exe
 (x86_64-win32-seh-rev1, Built by MinGW-W64 project) 4.8.3, 64-bit
 }}}


 In my opinion it should be returning 100 and I shouldn't be getting a
 warning about a mismatch.

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3822#comment:6>
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.