Changes between Version 7 and Version 8 of PostGISExtensionPaths


Ignore:
Timestamp:
02/11/22 10:54:41 (3 years ago)
Author:
robe
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PostGISExtensionPaths

    v7 v8  
    8282=== SOLUTION 3 ===
    8383
    84 The 0-byte file and strip model.  This approach creates 0 or very small byte files, with their existing solely to maintain PostgreSQL extension chain model.
    85 To reduce file bloat, we will only support the last two micros of any release.  Anyone who isn't in the latest micro (or latest to last micro) of each minor/major, with need to upgrade to said version OR use the postgis_extensions_upgrade() function.
     84The 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.
     85To 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.
    8686
    8787In this model, our extension files look like below:
    88 An additional addendum to this SOLUTION 3, is to not maintain - extensions/updateable.mk but instead have this file generated as part of the build process and be shipped as part of the tar ball.
    8988
    90 The extensions/updateable.mk will be generated by looking at git tags all the prior versions, and picking the last two of each mino.
    91 
    92 our generated extension upgrade scripts will look like the below, with only the postgis--3.3.0MAX--3.3.0.sql having any upgrade statements in it.
     89our generated extension upgrade scripts will look like the below, with only the postgis--3.3MAX--3.3.0.sql having any upgrade statements in it.
    9390
    9491----
    9592:
    96 postgis--3.1.4--3.3.0MAX.sql
    97 postgis--3.1.5--3.3.0MAX.sql
    98 postgis--3.2.0--3.3.0MAX.sql
    99 postgis--3.2.1--3.3.0MAX.sql
    100 postgis--3.3.0MAX--3.3.0.sql
     93postgis--3.1MAX--3.3MAX.sql
     94postgis--3.1.5--3.3MAX.sql
     95postgis--3.2MAX--3.3MAX.sql
     96postgis--3.3MAX--3.3.0.sql
     97postgis--3.3.0--3.3MAX.sql
    10198----
    10299**Benefits of this approach:**
    103100
    1041011. We are staying between the lines. Respecting known practices, but still having much lighter weight scripts.
    105 2. A little less clutter if we include the addendum (of only keeping the last 2)
     1022. A little less clutter, but we are relying on the user having the old version still installed so that they have a chain
     103postgis--<old-version-minor-micro>--<old-version-minor>MAX.sql
    1061043. A little little easier release cycle if we don't need to maintain extensions/updateable.mk and remember to update it.
    1071054. No change in upgrade extension workflow for packagers (or users who think of PostGIS as any other extension).