[postgis-devel] EXTENSION upgrades

[Paul Ramsey]

It could well be that we are "doing it wrong" to carry a micro version. However, if we stop doing so we lose the ability to patch plpgsql functions in micro fixes. And yeah, having a separate upgrade script for each micro is a PITA. But we do it. 
P

-- 
Paul Ramsey
http://cleverelephant.ca
http://postgis.net


On Tuesday, October 8, 2013 at 2:52 AM, Sandro Santilli wrote:

> Am I right that in order to do a "minor upgrade" with EXTENSION
> mechanism you need to have an explicit <oldversion>-<newversion>
> path from the old to the new version ?
> 
> How can this ever happen if stable branches are kept ?
> I mean, if we release a version 2.0.5, who's going to be ever
> producing a 2.0.5-2.1.0 file ?
> 
> Doesn't sound like a sustainable way to manage upgrades,
> or what am I missing ?
> 
> Do we need to extend the extension mechanism to deal with this
> kind of problems with a postgis_upgrade stored procedure of
> some sort ? How could that work ?
> 
> Or are we maybe doing it wrong to include micro version into
> the extension files ?
> 
> --strk; 
> 
> http://www.cartodb.com - Map, analyze and build applications with your data
> 
> ~~ http://strk.keybit.net 
> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org (mailto:postgis-devel at lists.osgeo.org)
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel