Changes between Version 20 and Version 21 of PostGISExtensionPaths

Timestamp:

07/29/22 22:33:40 (3 years ago)

Author:

strk

Comment:

Mark solution 1 as failing, with ticket reference

PostGISExtensionPaths

@@ -20 +20 @@
 
 
-== SOLTUION 1 ==
+== SOLUTION 1 (FAILS) ==
 
 This has already been committed in master branch for PostGIS 3.3.0.
@@ -32 +32 @@
 What it does:
 Update the current version to ANY and then run the updates.
-This has the affect of always forcing the  postgis--ANY--<current version>.sql script to run which handles all versions.
+This has the affect of always forcing the  postgis--ANY--
 
-Benefits of this approach:
-
-1. We only need to ship one extension upgrade script file per extension.  The postgis--ANY--<current version>.sql
-2. No clutter of 100s of 1000s of files.
-3. We don't need to maintain extensions/updateable.mk and remember to update it.
-4. It is possible to upgrade from postgis (older PostgreSQL Version) 3.3.0 to (new PostgreSQL version)  3.3.0. This is generally what is needed in pg_upgrade.
-
-**Drawbacks:** 
-
-1. People can only upgrade using 
-
-```
-SELECT postgis_extensions_upgrade();
-```
-Or do the manually mock with the pg_catalog.pg_extension table themselves
-
-2. We are mucking with system tables, pg_catalog.pg_extension, which we have done for other things, but is a questionable practice.
-
-3.  Packagers who have put in nice features to auto upgrade extensions during pg_upgrade, now have to treat us as special snowflakes.
-
-
+BLOCKER: this solution does not work in some cloud environments, see https://trac.osgeo.org/postgis/ticket/5194
 == SOLUTION 2 ==