[postgis-devel] EXTENSION upgrade scripts are now symlinks

[Paul Ramsey]

Once you're at 'next' there's nowhere to go. You end up with having to
upgrade from 'next' to 'next2' and so on :)
Anyways, agreed, I think we've long outgrown the extension version update
mechanism, but I'm unsure of what the correct thing to recommend to pgsql
team would be.

P

On Fri, Oct 6, 2017 at 3:16 AM, Sandro Santilli <strk at kbt.io> wrote:

> On Fri, Oct 06, 2017 at 04:55:58AM -0400, Regina Obe wrote:
> > Disregard my last question.  I forgot we changed a while ago after we
> dropped support for PostgreSQL 9.0 to just use DO to handle the differences
> in versions and just have  single upgrade script
>
> Exactly, PostGIS makes it easier to upgrade !
> The problem is only PostgreSQL which tries to make it harder..
>
> I actually wonder if we could have a single --next script
> so you could always do:
>
>  ALTER EXTENSION postgis UPDATE to 'next';
>
> And then the script would re-set pg_extension version
> to drop the "next" and keep the "final".
>
> I know, very cowboysh, but I'm really sick of all those files,
> even if they're now symlinks...
>
> --strk;
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20171006/17efcff3/attachment.html>