From da4041a3f62f5a87b2166a1566c9811ceb9c9f2c Mon Sep 17 00:00:00 2001 From: Darafei Praliaskouski Date: Mon, 11 Mar 2019 19:24:16 +0000 Subject: [PATCH] Doc layout improvements. Patch by Martin Davis. References #4332 Closes https://github.com/postgis/postgis/pull/380 git-svn-id: http://svn.osgeo.org/postgis/trunk@17335 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/Makefile.in | 3 +- doc/postgis.xml | 3 +- doc/reference.xml | 5 +- doc/reference_guc.xml | 5 +- doc/reference_management.xml | 638 +---------------------------- doc/reference_troubleshooting.xml | 162 ++++++++ doc/reference_type.xml | 103 +++-- doc/reference_version.xml | 641 ++++++++++++++++++++++++++++++ 8 files changed, 895 insertions(+), 665 deletions(-) create mode 100644 doc/reference_troubleshooting.xml create mode 100644 doc/reference_version.xml diff --git a/doc/Makefile.in b/doc/Makefile.in index 220d469dc..f93173e8b 100644 --- a/doc/Makefile.in +++ b/doc/Makefile.in @@ -124,7 +124,6 @@ XML_SOURCES = \ reference_accessor.xml \ reference_constructor.xml \ reference_editor.xml \ - reference_exception.xml \ reference_guc.xml \ reference_lrs.xml \ reference_management.xml \ @@ -137,7 +136,9 @@ XML_SOURCES = \ reference_raster.xml \ reference_temporal.xml \ reference_transaction.xml \ + reference_troubleshooting.xml \ reference_type.xml \ + reference_version.xml \ reference.xml \ release_notes.xml \ reporting.xml \ diff --git a/doc/postgis.xml b/doc/postgis.xml index d5238f991..98511fb35 100644 --- a/doc/postgis.xml +++ b/doc/postgis.xml @@ -41,7 +41,8 @@ - + + diff --git a/doc/reference.xml b/doc/reference.xml index 2e83606dc..0f420e7ac 100644 --- a/doc/reference.xml +++ b/doc/reference.xml @@ -17,7 +17,6 @@ &reference_type; - &reference_guc; &reference_management; &reference_constructor; &reference_accessor; @@ -31,6 +30,8 @@ &reference_temporal; &reference_transaction; &reference_misc; - &reference_exception; + &reference_version; + &reference_guc; + &reference_troubleshooting; diff --git a/doc/reference_guc.xml b/doc/reference_guc.xml index f41807cf9..f27ff53df 100644 --- a/doc/reference_guc.xml +++ b/doc/reference_guc.xml @@ -2,10 +2,11 @@ - This section lists custom PostGIS Grand Unified Custom Variables(GUC). These can be set globally, by database, by session or by transaction. Best set at global or database level. + This section lists custom PostGIS Grand Unified Custom Variables (GUC). +These can be set globally, by database, by session or by transaction. Best set at global or database level. - PostGIS Grand Unified Custom Variables (GUCs) + Grand Unified Custom Variables (GUCs) diff --git a/doc/reference_management.xml b/doc/reference_management.xml index e28c74ea8..fe3de247f 100644 --- a/doc/reference_management.xml +++ b/doc/reference_management.xml @@ -1,6 +1,13 @@ - Management Functions + + + These functions assist in defining tables containing geometry columns. + + + + + Table Management Functions @@ -344,635 +351,6 @@ DROP TABLE my_schema.my_spatial_table; - - - PostGIS_Extensions_Upgrade - - -Packages and upgrades postgis extensions (e.g. postgis_sfcgal, -postgis_topology, postgis_sfcgal) to latest available version. - - - - - - - text PostGIS_Extensions_Upgrade - - - - - - - - Description - - Packages and upgrades postgis extensions - to latest version. Only extensions you have installed in the - database will be packaged and upgraded if needed. - Reports full postgis version and build configuration infos after. - This is short-hand for doing multiple CREATE EXTENSION .. FROM - unpackaged and ALTER EXTENSION .. UPDATE for each postgis extension. - Currently only tries to upgrade extensions postgis, - postgis_raster, postgis_sfcgal, postgis_topology, and postgis_tiger_geocoder. - - Availability: 2.5.0 - - Changed: 3.0.0 to repackage loose extensions and support postgis_raster. - - - - - Examples - - SELECT PostGIS_Extensions_Upgrade(); - -NOTICE: Packaging extension postgis -NOTICE: Packaging extension postgis_raster -NOTICE: Packaging extension postgis_sfcgal -NOTICE: Extension postgis_topology is not available or not packagable for some reason -NOTICE: Extension postgis_tiger_geocoder is not available or not packagable for some reason - - postgis_extensions_upgrade ----------------------------------------------------------------------------------- -POSTGIS="3.0.0dev r16878" [EXTENSION] PGSQL="96" -GEOS="3.8.0dev-CAPI-1.11.0 a67b6f86" SFCGAL="1.3.5" PROJ="Rel. 4.9.3, -15 August 2016" GDAL="GDAL 2.3.0dev, released 2017/99/99" -LIBXML="2.9.4" LIBJSON="0.12.1" LIBPROTOBUF="1.2.1" TOPOLOGY -[UNPACKAGED!] RASTER -(1 row) - - - - See Also - - - , - , - , - , - , - - - - - - - - - - PostGIS_Full_Version - - Reports full postgis version and build configuration - infos. - - - - - - text PostGIS_Full_Version - - - - - - - - Description - - Reports full postgis version and build configuration - infos. Also informs about synchronization between - libraries and scripts suggesting upgrades as needed. - - - - Examples - - SELECT PostGIS_Full_Version(); - postgis_full_version ----------------------------------------------------------------------------------- -POSTGIS="3.0.0dev r17211" [EXTENSION] PGSQL="110" GEOS="3.8.0dev-CAPI-1.11.0 df24b6bb" SFCGAL="1.3.6" PROJ="Rel. 5.2.0, September 15th, 2018" -GDAL="GDAL 2.3.2, released 2018/09/21" LIBXML="2.9.9" LIBJSON="0.13.1" LIBPROTOBUF="1.3.1" WAGYU="0.4.3 (Internal)" TOPOLOGY RASTER -(1 row) - - - - - See Also - - - , - , - , - , - , - , - - - - - - - - PostGIS_GEOS_Version - - Returns the version number of the GEOS - library. - - - - - - text PostGIS_GEOS_Version - - - - - - - - Description - - Returns the version number of the GEOS library, or - NULL if GEOS support is not enabled. - - - - Examples - - SELECT PostGIS_GEOS_Version(); - postgis_geos_version ----------------------- - 3.1.0-CAPI-1.5.0 -(1 row) - - - - See Also - - , , , , - - - - - - PostGIS_Liblwgeom_Version - - Returns the version number of the liblwgeom - library. This should match the version of PostGIS. - - - - - - text PostGIS_Liblwgeom_Version - - - - - - - - Description - - Returns the version number of the liblwgeom library/ - - - - Examples - - SELECT PostGIS_Liblwgeom_Version(); -postgis_liblwgeom_version --------------------------- -2.3.3 r15473 -(1 row) - - - - See Also - - , , , , - - - - - - PostGIS_LibXML_Version - - Returns the version number of the libxml2 - library. - - - - - - text PostGIS_LibXML_Version - - - - - - - - Description - - Returns the version number of the LibXML2 library. - Availability: 1.5 - - - - Examples - - SELECT PostGIS_LibXML_Version(); - postgis_libxml_version ----------------------- - 2.7.6 -(1 row) - - - - See Also - - , , , , - - - - - - PostGIS_Lib_Build_Date - - Returns build date of the PostGIS library. - - - - - - text PostGIS_Lib_Build_Date - - - - - - - - Description - - Returns build date of the PostGIS library. - - - - Examples - - SELECT PostGIS_Lib_Build_Date(); - postgis_lib_build_date ------------------------- - 2008-06-21 17:53:21 -(1 row) - - - - - - PostGIS_Lib_Version - - Returns the version number of the PostGIS - library. - - - - - - text PostGIS_Lib_Version - - - - - - - - Description - - Returns the version number of the PostGIS library. - - - - Examples - - SELECT PostGIS_Lib_Version(); - postgis_lib_version ---------------------- - 1.3.3 -(1 row) - - - - See Also - - , , , , - - - - - - PostGIS_PROJ_Version - - Returns the version number of the PROJ4 - library. - - - - - - text PostGIS_PROJ_Version - - - - - - - - Description - - Returns the version number of the PROJ4 library, or - NULL if PROJ4 support is not enabled. - - - - Examples - - SELECT PostGIS_PROJ_Version(); - postgis_proj_version -------------------------- - Rel. 4.4.9, 29 Oct 2004 -(1 row) - - - - See Also - - , , , , - - - - - - PostGIS_Wagyu_Version - - Returns the version number of the internal Wagyu library. - - - - - - text PostGIS_Wagyu_Version - - - - - - - - Description - - Returns the version number of the internal Wagyu library, or - NULL if Wagyu support is not enabled. - - - - Examples - - SELECT PostGIS_Wagyu_Version(); - postgis_wagyu_version ------------------------ - 0.4.3 (Internal) -(1 row) - - - - See Also - - , , , , , - - - - - - PostGIS_Scripts_Build_Date - - Returns build date of the PostGIS scripts. - - - - - - text PostGIS_Scripts_Build_Date - - - - - - - - Description - - Returns build date of the PostGIS scripts. - - Availability: 1.0.0RC1 - - - - Examples - - SELECT PostGIS_Scripts_Build_Date(); - postgis_scripts_build_date -------------------------- - 2007-08-18 09:09:26 -(1 row) - - - - See Also - - , , , , - - - - - - PostGIS_Scripts_Installed - - Returns version of the postgis scripts installed in this - database. - - - - - - text PostGIS_Scripts_Installed - - - - - - - - Description - - Returns version of the postgis scripts installed in this - database. - - - If the output of this function doesn't match the output of - - you probably missed to properly upgrade an existing database. - See the Upgrading section for - more info. - - - Availability: 0.9.0 - - - - Examples - - SELECT PostGIS_Scripts_Installed(); - postgis_scripts_installed -------------------------- - 1.5.0SVN -(1 row) - - - - See Also - - , , - - - - - - PostGIS_Scripts_Released - - Returns the version number of the postgis.sql script - released with the installed postgis lib. - - - - - - text PostGIS_Scripts_Released - - - - - - - - Description - - Returns the version number of the postgis.sql script - released with the installed postgis lib. - - - Starting with version 1.1.0 this function returns the same - value of . Kept - for backward compatibility. - - - Availability: 0.9.0 - - - - Examples - - SELECT PostGIS_Scripts_Released(); - postgis_scripts_released -------------------------- - 1.3.4SVN -(1 row) - - - - See Also - - , , - - - - - - PostGIS_Version - - Returns PostGIS version number and compile-time - options. - - - - - - text PostGIS_Version - - - - - - - - Description - - Returns PostGIS version number and compile-time options. - - - - Examples - - SELECT PostGIS_Version(); - postgis_version ---------------------------------------- - 1.3 USE_GEOS=1 USE_PROJ=1 USE_STATS=1 -(1 row) - - - - See Also - - , , , , - - - Populate_Geometry_Columns diff --git a/doc/reference_troubleshooting.xml b/doc/reference_troubleshooting.xml new file mode 100644 index 000000000..607a9a8e3 --- /dev/null +++ b/doc/reference_troubleshooting.xml @@ -0,0 +1,162 @@ + + + + + These functions are utilities for troubleshooting and repairing geometry data. + They are only needed if the geometry data is corrupted in some way, + which should never happen under normal circumstances. + + + Troubleshooting Functions + + + + PostGIS_AddBBox + + Add bounding box to the geometry. + + + + + + geometry PostGIS_AddBBox + geometry geomA + + + + + + Description + + Add bounding box to the geometry. This would make bounding + box based queries faster, but will increase the size of the + geometry. + + + Bounding boxes are automatically added to geometries so in general this is not needed + unless the generated bounding box somehow becomes corrupted or you have an old install that is lacking bounding boxes. Then you need to drop the old and readd. + + + &curve_support; + + + + + Examples + + UPDATE sometable + SET the_geom = PostGIS_AddBBox(the_geom) + WHERE PostGIS_HasBBox(the_geom) = false; + + + + + See Also + + , + + + + + + PostGIS_DropBBox + + Drop the bounding box cache from the geometry. + + + + + + geometry PostGIS_DropBBox + geometry geomA + + + + + + Description + + Drop the bounding box cache from the geometry. This reduces + geometry size, but makes bounding-box based queries slower. It is also used to drop a corrupt bounding box. A tale-tell sign of a corrupt cached bounding box + is when your ST_Intersects and other relation queries leave out geometries that rightfully should return true. + + + Bounding boxes are automatically added to geometries and improve speed of queries so in general this is not needed + unless the generated bounding box somehow becomes corrupted or you have an old install that is lacking bounding boxes. + Then you need to drop the old and readd. This kind of corruption has been observed in 8.3-8.3.6 series whereby cached bboxes were not always recalculated when a geometry changed and upgrading to a newer version without a dump reload will not + correct already corrupted boxes. So one can manually correct using below and readd the bbox or do a dump reload. + + + &curve_support; + + + + + Examples + + --This example drops bounding boxes where the cached box is not correct + --The force to ST_AsBinary before applying Box2D forces a recalculation of the box, and Box2D applied to the table geometry always + -- returns the cached bounding box. + UPDATE sometable + SET the_geom = PostGIS_DropBBox(the_geom) + WHERE Not (Box2D(ST_AsBinary(the_geom)) = Box2D(the_geom)); + + UPDATE sometable + SET the_geom = PostGIS_AddBBox(the_geom) + WHERE Not PostGIS_HasBBOX(the_geom); + + + + + + + + See Also + + , , + + + + + + + PostGIS_HasBBox + + Returns TRUE if the bbox of this geometry is cached, FALSE otherwise. + + + + + + boolean PostGIS_HasBBox + geometry geomA + + + + + + Description + + Returns TRUE if the bbox of this geometry is cached, FALSE + otherwise. Use and to control caching. + + &curve_support; + + + + + Examples + + SELECT the_geom +FROM sometable WHERE PostGIS_HasBBox(the_geom) = false; + + + + + See Also + + , + + + + diff --git a/doc/reference_type.xml b/doc/reference_type.xml index 476db0cd0..62f1b0ebe 100644 --- a/doc/reference_type.xml +++ b/doc/reference_type.xml @@ -2,43 +2,65 @@ - This section lists the PostgreSQL data types installed by PostGIS. Note we describe the casting behavior of these which is very - important especially when designing your own functions. + This section lists the custom PostgreSQL + data types installed by PostGIS to represent spatial data. - A Cast is when one type is coerced into another type. PostgreSQL - is unique from most databases in that it allows you to define casting behavior for custom types and the functions used for casting. - A cast can be specified as automatic in which case, you do not have to do a CAST(myfoo As otherfootype) or myfoo::otherfootype - if you are feeding it to a function that only works with otherfootype and there is an automatic cast in place for it. - - The danger of relying on automatic cast behavior is when you have an overloaded function say one that takes a box2d and one that takes a box3d - but no geometry. What happens is that both functions are equally good to use with geometry since geometry has an autocast for both - -- so you end up with an ambiguous function error. To force PostgreSQL to choose, you do a CAST(mygeom As box3d) or mygeom::box3d. + Each data type describes its type casting behaviour. + A type cast converts values of one data type into another type. + PostgreSQL allows defining casting behavior for custom types, along with the functions used to convert type values. + Casts can be defined as automatic. + This allows PostgreSQL to automatically convert a function argument to a type supported by the function. + Casts can also be specified explicitly, + using the syntax CAST(myval As sometype) or myval::sometype. + This allows avoiding an issue that can occur when using an overloaded function which does not support a given type + (for example, one that accepts a box2d or a box3d, but not a geometry.) + Since geometry has an automatic cast to both box types, this will produce an "ambiguous function" error. + To prevent the error use an explicit cast to the desired box type. - At least as of PostgreSQL 8.3 - Everything can be CAST to text (presumably because of the magical unknown type), so no defined CASTS for that need to be present for you to CAST an object to text. + All data types can be CAST to text, so these do not need to be specified explicitly. - PostgreSQL PostGIS Geometry/Geography/Box Types + PostGIS Geometry/Geography/Box Data Types box2d - A box composed of x min, ymin, xmax, ymax. Often used to return the 2d enclosing box of a geometry. + A 2-dimensional bounding box. + Often used to describe the 2D extent of a geometry or collection of geometries. Description - box2d is a spatial data type used to represent the enclosing box of a geometry or set of geometries. ST_Extent in earlier versions prior to PostGIS 1.4 would return a box2d. + box2d is a spatial data type used to represent + the two-dimensional enclosing box of a geometry or collection of geometries. + For example, the aggregate function returns a box2d object. + The representation contains the values xmin, ymin, xmax, ymax. + These are the minimum and maxium values of the X and Y extents. + + + + See Also + + + box3d - A box composed of x min, ymin, zmin, xmax, ymax, zmax. Often used to return the 3d extent of a geometry or collection of geometries. + A 3-dimensional bounding box. + Often used to describe the 3D extent of a geometry or collection of geometries. Description - box3d is a postgis spatial data type used to represent the enclosing box of a geometry or set of geometries. ST_3DExtent returns a box3d object. + box3d is a postgis spatial data type used to represent + the three-dimensional enclosing box of a geometry or collection of geometries. + For example, the aggregate function returns a box3d object. + + The representation contains the values xmin, ymin, zmin, xmax, ymax, zmax. + These are the minimum and maxium values of the X, Y and Z extents. + @@ -67,18 +89,24 @@ + + + See Also + + + geometry - Planar spatial data type. + The type representing spatial features with planar coordinate systems. Description - geometry is a fundamental PostGIS spatial data type used to represent a feature in the Euclidean coordinate system. - All spatial operations on geometry are using units of the Spatial Reference System the geomtry is in. + geometry is a fundamental PostGIS spatial data type used to represent a feature in planar (Euclidean) coordinate systems. + All spatial operations on geometry use the units of the Spatial Reference System the geometry is in. @@ -122,23 +150,34 @@ See Also - + , geometry_dump - A spatial datatype with two fields - geom (holding a geometry object) - and path[] (a 1-d array holding the position of the geometry within the dumped object.) + A composite type used to describe the parts of complex geometry. Description - geometry_dump is a compound data type consisting of a geometry object referenced by the .geom field - and path[] a 1-dimensional integer array (starting at 1 e.g. path[1] to get first element) array that defines the navigation path within the dumped geometry to find this element. - It is used by the ST_Dump* family of functions as an output type to explode a more complex geometry into its - constituent parts and location of parts. + geometry_dump is a + composite data type + containing the fields: + + + geom - a references to a component geometry + + + path[] - a 1-dimensional integer array + that defines the navigation path within the dumped geometry to the geom component. + The path array starts at 1 (e.g. path[1] is the first element.) + + + + It is used by the ST_Dump* family of functions as an output type to explode a complex geometry into its + constituent parts. See Also @@ -149,12 +188,18 @@ geography - Ellipsoidal spatial data type. + The type representing spatial features with geodetic (ellipsoidal) coordinate systems. Description - geography is a spatial data type used to represent a feature in the round-earth coordinate system. + geography is a spatial data type used to represent a feature in geodetic coordinate systems. + Geodetic coordinate systems model the earth using an ellipsoid. + + + Spatial operations on the geography type provide more accurate results + by taking the ellipsoidal model into account. + @@ -178,7 +223,7 @@ See Also - , + , diff --git a/doc/reference_version.xml b/doc/reference_version.xml new file mode 100644 index 000000000..346232657 --- /dev/null +++ b/doc/reference_version.xml @@ -0,0 +1,641 @@ + + + + + These functions report and upgrade PostGIS versions. + + + + + Version Functions + + + + PostGIS_Extensions_Upgrade + + +Packages and upgrades postgis extensions (e.g. postgis_raster, +postgis_topology, postgis_sfcgal) to latest available version. + + + + + + + text PostGIS_Extensions_Upgrade + + + + + + + + Description + + Packages and upgrades postgis extensions + to latest version. Only extensions you have installed in the + database will be packaged and upgraded if needed. + Reports full postgis version and build configuration infos after. + This is short-hand for doing multiple CREATE EXTENSION .. FROM + unpackaged and ALTER EXTENSION .. UPDATE for each postgis extension. + Currently only tries to upgrade extensions postgis, + postgis_raster, postgis_sfcgal, postgis_topology, and postgis_tiger_geocoder. + + Availability: 2.5.0 + + Changed: 3.0.0 to repackage loose extensions and support postgis_raster. + + + + + Examples + + SELECT PostGIS_Extensions_Upgrade(); + +NOTICE: Packaging extension postgis +NOTICE: Packaging extension postgis_raster +NOTICE: Packaging extension postgis_sfcgal +NOTICE: Extension postgis_topology is not available or not packagable for some reason +NOTICE: Extension postgis_tiger_geocoder is not available or not packagable for some reason + + postgis_extensions_upgrade +---------------------------------------------------------------------------------- +POSTGIS="3.0.0dev r16878" [EXTENSION] PGSQL="96" +GEOS="3.8.0dev-CAPI-1.11.0 a67b6f86" SFCGAL="1.3.5" PROJ="Rel. 4.9.3, +15 August 2016" GDAL="GDAL 2.3.0dev, released 2017/99/99" +LIBXML="2.9.4" LIBJSON="0.12.1" LIBPROTOBUF="1.2.1" TOPOLOGY +[UNPACKAGED!] RASTER +(1 row) + + + + See Also + + + , + , + , + , + , + + + + + + + + + + PostGIS_Full_Version + + Reports full postgis version and build configuration + infos. + + + + + + text PostGIS_Full_Version + + + + + + + + Description + + Reports full postgis version and build configuration + infos. Also informs about synchronization between + libraries and scripts suggesting upgrades as needed. + + + + Examples + + SELECT PostGIS_Full_Version(); + postgis_full_version +---------------------------------------------------------------------------------- +POSTGIS="3.0.0dev r17211" [EXTENSION] PGSQL="110" GEOS="3.8.0dev-CAPI-1.11.0 df24b6bb" SFCGAL="1.3.6" PROJ="Rel. 5.2.0, September 15th, 2018" +GDAL="GDAL 2.3.2, released 2018/09/21" LIBXML="2.9.9" LIBJSON="0.13.1" LIBPROTOBUF="1.3.1" WAGYU="0.4.3 (Internal)" TOPOLOGY RASTER +(1 row) + + + + + See Also + + + , + , + , + , + , + , + + + + + + + + PostGIS_GEOS_Version + + Returns the version number of the GEOS + library. + + + + + + text PostGIS_GEOS_Version + + + + + + + + Description + + Returns the version number of the GEOS library, or + NULL if GEOS support is not enabled. + + + + Examples + + SELECT PostGIS_GEOS_Version(); + postgis_geos_version +---------------------- + 3.1.0-CAPI-1.5.0 +(1 row) + + + + See Also + + , , , , + + + + + + PostGIS_Liblwgeom_Version + + Returns the version number of the liblwgeom + library. This should match the version of PostGIS. + + + + + + text PostGIS_Liblwgeom_Version + + + + + + + + Description + + Returns the version number of the liblwgeom library/ + + + + Examples + + SELECT PostGIS_Liblwgeom_Version(); +postgis_liblwgeom_version +-------------------------- +2.3.3 r15473 +(1 row) + + + + See Also + + , , , , + + + + + + PostGIS_LibXML_Version + + Returns the version number of the libxml2 + library. + + + + + + text PostGIS_LibXML_Version + + + + + + + + Description + + Returns the version number of the LibXML2 library. + Availability: 1.5 + + + + Examples + + SELECT PostGIS_LibXML_Version(); + postgis_libxml_version +---------------------- + 2.7.6 +(1 row) + + + + See Also + + , , , , + + + + + + PostGIS_Lib_Build_Date + + Returns build date of the PostGIS library. + + + + + + text PostGIS_Lib_Build_Date + + + + + + + + Description + + Returns build date of the PostGIS library. + + + + Examples + + SELECT PostGIS_Lib_Build_Date(); + postgis_lib_build_date +------------------------ + 2008-06-21 17:53:21 +(1 row) + + + + + + PostGIS_Lib_Version + + Returns the version number of the PostGIS + library. + + + + + + text PostGIS_Lib_Version + + + + + + + + Description + + Returns the version number of the PostGIS library. + + + + Examples + + SELECT PostGIS_Lib_Version(); + postgis_lib_version +--------------------- + 1.3.3 +(1 row) + + + + See Also + + , , , , + + + + + + PostGIS_PROJ_Version + + Returns the version number of the PROJ4 + library. + + + + + + text PostGIS_PROJ_Version + + + + + + + + Description + + Returns the version number of the PROJ4 library, or + NULL if PROJ4 support is not enabled. + + + + Examples + + SELECT PostGIS_PROJ_Version(); + postgis_proj_version +------------------------- + Rel. 4.4.9, 29 Oct 2004 +(1 row) + + + + See Also + + , , , , + + + + + + PostGIS_Wagyu_Version + + Returns the version number of the internal Wagyu library. + + + + + + text PostGIS_Wagyu_Version + + + + + + + + Description + + Returns the version number of the internal Wagyu library, or + NULL if Wagyu support is not enabled. + + + + Examples + + SELECT PostGIS_Wagyu_Version(); + postgis_wagyu_version +----------------------- + 0.4.3 (Internal) +(1 row) + + + + See Also + + , , , , , + + + + + + PostGIS_Scripts_Build_Date + + Returns build date of the PostGIS scripts. + + + + + + text PostGIS_Scripts_Build_Date + + + + + + + + Description + + Returns build date of the PostGIS scripts. + + Availability: 1.0.0RC1 + + + + Examples + + SELECT PostGIS_Scripts_Build_Date(); + postgis_scripts_build_date +------------------------- + 2007-08-18 09:09:26 +(1 row) + + + + See Also + + , , , , + + + + + + PostGIS_Scripts_Installed + + Returns version of the postgis scripts installed in this + database. + + + + + + text PostGIS_Scripts_Installed + + + + + + + + Description + + Returns version of the postgis scripts installed in this + database. + + + If the output of this function doesn't match the output of + + you probably missed to properly upgrade an existing database. + See the Upgrading section for + more info. + + + Availability: 0.9.0 + + + + Examples + + SELECT PostGIS_Scripts_Installed(); + postgis_scripts_installed +------------------------- + 1.5.0SVN +(1 row) + + + + See Also + + , , + + + + + + PostGIS_Scripts_Released + + Returns the version number of the postgis.sql script + released with the installed postgis lib. + + + + + + text PostGIS_Scripts_Released + + + + + + + + Description + + Returns the version number of the postgis.sql script + released with the installed postgis lib. + + + Starting with version 1.1.0 this function returns the same + value of . Kept + for backward compatibility. + + + Availability: 0.9.0 + + + + Examples + + SELECT PostGIS_Scripts_Released(); + postgis_scripts_released +------------------------- + 1.3.4SVN +(1 row) + + + + See Also + + , , + + + + + + PostGIS_Version + + Returns PostGIS version number and compile-time + options. + + + + + + text PostGIS_Version + + + + + + + + Description + + Returns PostGIS version number and compile-time options. + + + + Examples + + SELECT PostGIS_Version(); + postgis_version +--------------------------------------- + 1.3 USE_GEOS=1 USE_PROJ=1 USE_STATS=1 +(1 row) + + + + See Also + + , , , , + + + + -- 2.49.0