From d170a3ff1600559cf0510a2b6d6cce0a45ed1a3c Mon Sep 17 00:00:00 2001 From: Regina Obe Date: Mon, 11 Jun 2012 14:02:51 +0000 Subject: [PATCH] warnings should be more prominent. Move extension warning up a bit. correct misspelling git-svn-id: http://svn.osgeo.org/postgis/trunk@9877 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/html/style.css | 1 + doc/installation.xml | 11 ++++++----- 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/doc/html/style.css b/doc/html/style.css index 1c933da62..76c4857d5 100644 --- a/doc/html/style.css +++ b/doc/html/style.css @@ -30,6 +30,7 @@ pre, .literallayout { border-right-width: 0px; border-left-width: 0px; border-bo .note { border-left-width: 0px; border-bottom-width: 2px; border-right-width: 0px; border-top-width: 2px; width: 80%; border-color: #a2d545; border-style: solid; font-size: 11px; margin-bottom: 10px; margin-top: 10px; overflow: auto; padding: 10px; background: #e4f7dd; -moz-border-radius: 2px; -webkit-border-radius: 2px;} /* code { border-right-style: solid; border-right-color: #79791a; border-left-color: #79791b; border-left-style: solid; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px; border-top-width: 0px; padding-left: 3px; padding-bottom: 1px; padding-right: 3px; padding-top: 1px; font-family: "Courier New", Courier, Monaco, monospace; color: #fefff7; background: #9b9e96; -moz-border-radius: 2px; -webkit-border-radius: 2px;} */ .programlisting {font-family: "Courier New", Courier, Monaco, monospace;} +.warning { border-left-width: 0px; border-bottom-width: 2px; border-right-width: 0px; border-top-width: 2px; width: 80%; border-color: #a2d545; border-style: solid; font-size: 11px; margin-bottom: 10px; margin-top: 10px; overflow: auto; padding: 10px; background: #FFBF00; -moz-border-radius: 2px; -webkit-border-radius: 2px;} /* 4. Docbook Specifics ----------------------------------------------------- */ diff --git a/doc/installation.xml b/doc/installation.xml index bf630dd58..cb6e878b3 100644 --- a/doc/installation.xml +++ b/doc/installation.xml @@ -605,16 +605,17 @@ in the extensions section of the database browser tree and wi CREATE EXTENSION postgis; CREATE EXTENSION postgis_topology; +Extension tables spatial_ref_sys, layer, topology can not be explicitly backed up. They can only +be backed up when the respective postgis or postgis_topology extension is backed up, which only seems to happen when you backup the whole database. +As of PostGIS 2.0.1, only srid records not packaged with PostGIS are backed up when the database is backed up so don't go around changing srids we package and expect your changes to be there. Put in a ticket if you find an issue. The structures of extension tables are never backed up since they are created with CREATE EXTENSION +and assumed to be the same for a given version of an extension. These behaviors are built into the current PostgreSQL extension model, so nothing we can do about it. + If you installed &last_release_version;, without using our wonderful extension system, you can change it to be extension based by first upgrading to the latest micro version running the upgrade scripts: postgis_upgrade_20_minor.sql,raster_upgrade_20_minor.sql,topology_upgrade_20_minor.sql. If you installed postgis without raster support, you'll need to install raster support first (using the full rtpostgis.sql -Then you can run teh below commands to package the functions in their respective extension. +Then you can run the below commands to package the functions in their respective extension. CREATE EXTENSION postgis FROM unpackaged; CREATE EXTENSION postgis_topology FROM unpackaged; -Extension tables spatial_ref_sys, layer, topology can not be explicitly backed up. They can only -be backed up when the respective postgis or postgis_topology extension is backed up, which only seems to happen when you backup the whole database. -As of PostGIS 2.0.1, only srid records not packaged with PostGIS are backed up when the database is backed up so don't go around changing srids we package and expect your changes to be there. Put in a ticket if you find an issue. The structures of extension tables are never backed up since they are created with CREATE EXTENSION -and assumed to be the same for a given version of an extension. These behaviors are built into the current PostgreSQL extension model, so nothing we can do about it. -- 2.50.1