[postgis-devel] Upgrade strategies (was: PSC Vote: Get rid of micro in PostGIS Extension scripts)

[Regina Obe]

> On Wed, Jun 08, 2022 at 01:06:02PM -0400, Regina Obe wrote:
> > Sandro wrote:
> >
> > > I find the naming confusing, wouldn't this be clearer if it was:
> > >
> > >   postgis--3.0.0--ANY.sql (0 bytes)
> > >   postgis--ANY--3.3.0.sql (real upgrade)
> > >
> > > We'd then be moving along the same track we are already on
> >
> > I'm fine with that change. Only minor issues I see with this is:
> >
> > 1) postgis-3.0.0--ANY.sql and friends will be carried by both 3.3.0
> > and
> > 3.4.0 releases.  Debian might have issue with this since I think they
> > package the scripts in a separate package.  But at least the files
> > will all be the same.
> 
> Ah yes, now I remember why Paul came up with the other idea of an "MAX"
> per-branch version:
> 
>   postgis-3.0.0--3.0.MAX.sql
>   postgis-3.0.MAX--ANY.sql
> 
> But it would still have the same problem, when upgrading to 3.0.1, right ?
> Or is Paul proposal taking care of this issue ?
> 
> 
> --strk;
> 
>   Libre GIS consultant/developer
>   https://strk.kbt.io/services.html

It's not an issue because we don't support installing two different micro
versions in the same instance.
Micros ideally should be replacing the existing files of same minor, so it's
actually more in line with what people expect.

-- Regina Obe;