[postgis-devel] [PostGIS] #1944: Extensions Migration path from 2.1.0 to 2.1.0

[Bborie Park]

I'm not posting this on the ticket as I don't want to hijack the
ticket.  Yesterday, I tried migrating a 2.0 database to 2.1 and after
some tweaking, it actually worked.  I used
postgis_upgrade_20_minor.sql and rtpostgis_upgrade_20_minor.sql.

The only change I made to postgis_upgrade_20_minor.sql was in the
function postgis_major_version_check() where I hardcoded the value of
"old_scripts" as postgis_lib_version() failed as postgis-2.0.so didn't
exist anymore (had upgraded the underlying library to 2.1 already).

For rtpostgis_upgrade_20_minor.sql, I had to add back two new types
(agg_samealignment and addbandarg).

-bborie

On Fri, Aug 3, 2012 at 6:04 AM, PostGIS <trac at osgeo.org> wrote:
> #1944: Extensions Migration path from 2.1.0 to 2.1.0
> -----------------------------------+----------------------------------------
>  Reporter:  robe                   |       Owner:  robe
>      Type:  defect                 |      Status:  new
>  Priority:  critical               |   Milestone:  PostGIS 2.1.0
> Component:  build/upgrade/install  |     Version:  trunk
>  Keywords:                         |
> -----------------------------------+----------------------------------------
>
> Comment(by strk):
>
>  or is the version of the script really only found in the file itself ?
>  Because we could then have the file contain the version including SVN
>  revision id and always use the same syntax (every run will find a
>  different version in the script)
>
> --
> Ticket URL: <http://trac.osgeo.org/postgis/ticket/1944#comment:3>
> PostGIS <http://trac.osgeo.org/postgis/>
> The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel