[postgis-tickets] [SCM] PostGIS branch master updated. 69865c307e1de61a5ab9332e78d708e8a4169b5d
git at osgeo.org
git at osgeo.org
Wed Jan 15 11:01:33 PST 2020
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "PostGIS".
The branch, master has been updated
via 69865c307e1de61a5ab9332e78d708e8a4169b5d (commit)
from f023465e0fed5afb7690f4cbeb576631995fb5a6 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 69865c307e1de61a5ab9332e78d708e8a4169b5d
Author: Regina Obe <lr at pcorp.us>
Date: Wed Jan 15 14:01:27 2020 -0500
Minor code formatting so doesn't have weird break lines in programlisting
diff --git a/doc/installation.xml b/doc/installation.xml
index 1bd8a74..6efa4f9 100644
--- a/doc/installation.xml
+++ b/doc/installation.xml
@@ -1908,46 +1908,41 @@ environment).</para></note>
not using extensions. If you have extensions and try to
upgrade with this approach you'll get messages like:</para>
- <programlisting>can't drop ... because postgis extension depends on it</programlisting>
+ <programlisting>can't drop ... because postgis extension depends on it</programlisting>
- <para>
- NOTE: if you are moving from PostGIS 1.* to PostGIS 2.* or from
+ <para>NOTE: if you are moving from PostGIS 1.* to PostGIS 2.* or from
PostGIS 2.* prior to r7409, you cannot use this procedure but
- would rather need to do a
+ would rather need to do a
<link linkend="hard_upgrade">HARD UPGRADE</link>.
- </para>
+ </para>
- <para>
- After compiling and installing (make install) you should
- find a set of <filename>*_upgrade.sql</filename>
- files in the installation folders. You can list
- them all with:
- </para>
+ <para>
+ After compiling and installing (make install) you should
+ find a set of <filename>*_upgrade.sql</filename>
+ files in the installation folders. You can list
+ them all with:
+ </para>
- <programlisting>
- ls `pg_config --sharedir`/contrib/postgis-&last_release_version;/*_upgrade.sql
- </programlisting>
+ <programlisting>ls `pg_config --sharedir`/contrib/postgis-&last_release_version;/*_upgrade.sql</programlisting>
<para>
- Load them all in turn, starting from <filename>postgis_upgrade.sql</filename>.
- </para>
+ Load them all in turn, starting from <filename>postgis_upgrade.sql</filename>.
+ </para>
- <programlisting>
- psql -f postgis_upgrade.sql -d your_spatial_database
- </programlisting>
+ <programlisting>psql -f postgis_upgrade.sql -d your_spatial_database</programlisting>
- <para>
- The same procedure applies to raster,
- topology and sfcgal extensions, with upgrade files named
- <filename>rtpostgis_upgrade.sql</filename>,
- <filename>topology_upgrade.sql</filename> and
- <filename>sfcgal_upgrade.sql</filename> respectively.
- If you need them:
- </para>
+ <para>
+ The same procedure applies to raster,
+ topology and sfcgal extensions, with upgrade files named
+ <filename>rtpostgis_upgrade.sql</filename>,
+ <filename>topology_upgrade.sql</filename> and
+ <filename>sfcgal_upgrade.sql</filename> respectively.
+ If you need them:
+ </para>
- <programlisting>psql -f rtpostgis_upgrade.sql -d your_spatial_database</programlisting>
- <programlisting>psql -f topology_upgrade.sql -d your_spatial_database</programlisting>
- <programlisting>psql -f sfcgal_upgrade.sql -d your_spatial_database</programlisting>
+ <programlisting>psql -f rtpostgis_upgrade.sql -d your_spatial_database</programlisting>
+ <programlisting>psql -f topology_upgrade.sql -d your_spatial_database</programlisting>
+ <programlisting>psql -f sfcgal_upgrade.sql -d your_spatial_database</programlisting>
<note>
<para>
-----------------------------------------------------------------------
Summary of changes:
doc/installation.xml | 55 ++++++++++++++++++++++++----------------------------
1 file changed, 25 insertions(+), 30 deletions(-)
hooks/post-receive
--
PostGIS
More information about the postgis-tickets
mailing list