Opened 5 years ago
Closed 4 years ago
#4644 closed defect (fixed)
postgis_full_version doesn't include hash
Reported by: | robe | Owned by: | robe |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 3.0.2 |
Component: | build | Version: | 3.0.x |
Keywords: | Cc: |
Description
Not sure how I missed it before, but just noticed I must have put the wrong variable in output.
Cause when I did after testing out windows installer
SELECT postgis_full_version();
Got this:
POSTGIS="3.0.1 r3.0.1" [EXTENSION] PGSQL="120" GEOS="3.8.0-CAPI-1.13.1 " PROJ="Rel. 5.2.0, September 15th, 2018" GDAL="GDAL 2.4.4, released 2020/01/08" LIBXML="2.9.9" LIBJSON="0.12" LIBPROTOBUF="1.2.1" WAGYU="0.4.3 (Internal)" (core procs from "3.0.0 r17983" need upgrade) TOPOLOGY (topology procs from "3.0.0 r17983" need upgrade) RASTER (raster procs from "3.0.0 r17983" need upgrade)
and then after running:
SELECT postgis_extensions_upgarde(); SELECT postgis_full_version();
Got this:
POSTGIS="3.0.1 3.0.1" [EXTENSION] PGSQL="120" GEOS="3.8.0-CAPI-1.13.1 " PROJ="Rel. 5.2.0, September 15th, 2018" GDAL="GDAL 2.4.4, released 2020/01/08" LIBXML="2.9.9" LIBJSON="0.12" LIBPROTOBUF="1.2.1" WAGYU="0.4.3 (Internal)" TOPOLOGY RASTER
Note:
See TracTickets
for help on using tickets.
I thought has was omitted when we were in a tag. That's actually what
git describe
returns, when current hash matches a tag.