[postgis-devel] PSC Vote: Get rid of micro in PostGIS Extension scripts (and comments from others)

[Sandro Santilli]

On Thu, Jun 23, 2022 at 03:37:03PM -0400, Regina Obe wrote:
> > > So how about this so we keep the ANY as final target:
> > >
> > > postgis--2.0.0--3.3.MAX.sql -> 0 byte file postgis--3.3.MAX--3.3.0.sql
> > > -> postgis--ANY-3.3.0.sql  (this can still be a
> > > symlink)
> > > it will still be fatter than just making any a 0 byte, but I can live
> > > with having two fat files on windows.
> > 
> > How's this different from:
> > 
> >   postgis--2.0.0--ANY.sql  (0 bytes)
> >   postgis--ANY-3.3.0.sql (the only upgrade script)
> > 
> > --strk;
> [Regina Obe] 
> Because we don't want
> 
> postgis--2.0.0--ANY.sql  
> 
> as that gets overwritten with every single minor install.

A file named `postgis--2.0.0--ANY.sql` would NOT be overritten
with upgrades as in my view that file would be installed by
PostGIS-2.0.0 and nothing more.

The solution I'm proposing is:

  Each new release X.Y.Z ships:

    - postgis--X.Y.Z--ANY.sql  (0 bytes)
    - postgis--ANY-X.Y.Z.sql (the only upgrade script)

This will only solve the problem from this point in time on,
upgrades from OLDER releases of PostGIS would still need to
be dealt with in some way, so the MAX idea could be used
for that, maybe back-installing for each old release their
corresponding 0-bytes file postgis--X.Y.Z--ANY.sql but only if
missing ?

--strk;