Context Navigation

Changes between Version 13 and Version 14 of PostGISExtensionPaths

-              v13
+              v14
 The 0-byte file and strip model.  This approach creates 0 or very small byte files, with their existense solely to maintain PostgreSQL extension chain model.
+To reduce file bloat, we will have <version-minor>--<version-minor-curren>MAX files.  Anyone who is coming from a prior minor will have a file such as postgis--3.2.1--3.2MAX version OR use the postgis_extensions_upgrade() function.
+Still up for discussion: **To reduce file bloat, we will have <version-minor>.X--<version-minor-current> files**.
+We will keep 2 micros before for each minor, just in case the user uninstalled the prior minor before installing the new one.
-In this model, our extension files look like below:
+our generated extension upgrade scripts will look like the below, with only the postgis--3.3.X--3.3.0.sql having any upgrade statements in it.
+The assumption is anyone coming from a prior minor will have a file such as postgis--3.2.1--3.2.X version OR use the postgis_extensions_upgrade() function.
+In this model, our generated extension upgrade scripts will look like the below, with only the postgis--3.3.X--3.3.0.sql having any upgrade statements in it.
 ----
 {{{
+:
 postgis--3.0.3--3.3.X.sql
+postgis--3.0.4--3.3.X.sql
 postgis--3.0.5--3.3.X.sql
 postgis--3.0.X--3.3.X.sql
 …
 postgis--3.1.4--3.3.X.sql
 postgis--3.1.5--3.3.X.sql
+postgis--3.2.0--3.3.X.sql
+postgis--3.2.1--3.3.X.sql
 postgis--3.2.X--3.3.X.sql
 postgis--3.3.X--3.3.0.sql