[postgis-devel] ALTER EXTENSION postgis UPGRADE to '2.1.1'

[Paul Ramsey]

This is ticketed here now, http://trac.osgeo.org/postgis/ticket/2510
in anticipation of putting a fix in.

On Tue, Oct 15, 2013 at 1:59 PM, Paul Ramsey <pramsey at cleverelephant.ca> wrote:
> The function ends up in a file named thusly:
>
> postgis_upgrade_20_21.sql
>
> So, we've got a "make sure it isn't 1.X" check, in a script which is
> clearly named to allow for upgrades from 2.0 to 2.1. I think it's safe
> to remove it entirely.
>
> P
>
> On Tue, Sep 24, 2013 at 1:55 AM, Sandro Santilli <strk at keybit.net> wrote:
>> Can that call be _only_ removed from EXTENSION scripts ?
>> I also pre-date extensions and not sure I want to go there before
>> those 10 years ;)
>>
>> --strk;
>>
>> On Mon, Sep 23, 2013 at 01:29:42PM -0700, Paul Ramsey wrote:
>>> This has been failing for people using packages to manage their
>>> postgis, because upgrading their postgis2 package is removing the old
>>> postgis-2.0.so and installing a postgis-2.1.so file.
>>>
>>> I isolated the problem while on the plane, it's the temporary
>>> postgis_major_version_check function, which calls a library function
>>> during installation. I think it'll take a half day of careful thinking
>>> and testing to get a fix that both works on existing installations and
>>> also does the right thing, which I think is to get rid of that routine
>>> entirely. It's very old and pre-dates extensions, and we don't have an
>>> upgrade_15_21 script anyways. We can add a replacement in 10 years
>>> when we do 3.0
>>>
>>> P.
>>> _______________________________________________
>>> postgis-devel mailing list
>>> postgis-devel at lists.osgeo.org
>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel