[postgis-users] fail to upgrade from 2.1.8 to 2.2.2 or 2.3.3

[Sandro Santilli]

On Thu, Jun 27, 2019 at 06:55:39PM +0200, olivier.lobry at umontpellier.fr wrote:
> 
> > Le 27 juin 2019 à 17:59, Sandro Santilli <strk at kbt.io> a écrit :
> > 
> > On Thu, Jun 27, 2019 at 12:46:03PM +0200, olivier.lobry at umontpellier.fr wrote:
> > 
> >> at line 248, substring(upgraded from '[0-9]*\.([0-9]*)\.’) cannot be cast to int since it leads ‘’ because of the « SELECT '2.2'::text as upgraded » at line 242.
> >> 
> >> replacing SELECT '2.2'::text as upgraded with SELECT ‘2.2.2'::text as upgraded solves the issue
> >> 
> >> Looks like there is the same problem with any migration scripts from 2.1.xx 
> >> 
> >> Maybe a problem of compilation/debian distribution (since I installed postgis using debian packages) ?
> > 
> > I guess we could just pick the first two numbers and drop the final
> > '\.' portion of the regexp... What surprises me is that our CI bots
> > testing upgrades did not catch this issue.
> 
> yes and what surprises me is that the statement is wrong whatever the database it is ran against (since the ‘2.2’ is hard coded)

I suggest you file a ticket to https://trac.osgeo.org/postgis
as you may have found a serious bug.

--strk;