[postgis-tickets] [SCM] postgis.net branch hugo updated. d5cefbd7045905e7540d96deb4439a1e1616a882

[git at osgeo.org]

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.net".

The branch, hugo has been updated
       via  d5cefbd7045905e7540d96deb4439a1e1616a882 (commit)
      from  ceb3203ccad7daeead3d8d12c0b8548357b40a98 (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 d5cefbd7045905e7540d96deb4439a1e1616a882
Author: Regina Obe <lr at pcorp.us>
Date:   Mon Feb 28 03:05:25 2022 -0500

    More cleanup

diff --git a/content/post/2017/06-05_postgis-backend-is-already-set.html b/content/post/2017/06-05_postgis-backend-is-already-set.md
similarity index 93%
rename from content/post/2017/06-05_postgis-backend-is-already-set.html
rename to content/post/2017/06-05_postgis-backend-is-already-set.md
index 492bce4..08daaf7 100644
--- a/content/post/2017/06-05_postgis-backend-is-already-set.html
+++ b/content/post/2017/06-05_postgis-backend-is-already-set.md
@@ -4,9 +4,9 @@ layout: post
 category: tips
 tags: [newbie, upgrade]
 author: Regina Obe
+date: "2017-06-05"
 thumbnail: postgis.png
 ---
-<--markdown-->
 
 The error 'postgis.backend' is already set comes up every so often in PostGIS mailing list.
 The issue arises often during or after an upgrade. I'll go over causes for this I am aware of and how to fix.
@@ -33,11 +33,11 @@ The fix for this is to run the old **legacy_uninstall.sql** and reinstall the ne
 So for example, if I had 2.1 legacy scripts installed and I'm on ubuntu.
 I would connect to by database using psql:
 
-{% geshi 'sh' %}
+```sh
 \connect gisdb
 \i /usr/share/postgresql/9.4/contrib/postgis-2.1/uninstall_legacy.sql
 
--- only if you want still need legacy functions
+# only if you want still need legacy functions
 \i /usr/share/postgresql/9.4/contrib/postgis-2.3/legacy.sql
 ```
 
@@ -91,22 +91,21 @@ ORDER BY probin;
 In a good, install, you should have only one row that looks something like
 this.  Your version number might be different.
 
-<pre>
-		probin       | count
----------------------+-------
- $libdir/postgis-2.4 |   446
-(1 row)
-</pre>
+
+	|   probin            | count |
+	|---------------------|-------|
+	|$libdir/postgis-2.4  |   446 |
+
+
 
 If you have more than one row, such as:
 
-<pre>
-		probin       | count
+| probin               | count
 ---------------------+-------
  $libdir/postgis-2.4 |   446
   $libdir/postgis-2.1 |   4
 (1 row)
-</pre>
+
 
 
 then run this query to list the offending functions

-----------------------------------------------------------------------

Summary of changes:
 ...tml => 06-05_postgis-backend-is-already-set.md} | 23 +++++++++++-----------
 1 file changed, 11 insertions(+), 12 deletions(-)
 rename content/post/2017/{06-05_postgis-backend-is-already-set.html => 06-05_postgis-backend-is-already-set.md} (93%)


hooks/post-receive
-- 
postgis.net