[postgis-tickets] [PostGIS] #2960: Note in soft upgrade docs that legacy.sql needs to be rerun for each minor upgrade

[PostGIS]

#2960: Note in soft upgrade docs that legacy.sql needs to be rerun for each minor
upgrade
---------------------------+------------------------------------------------
 Reporter:  robe           |       Owner:  robe         
     Type:  defect         |      Status:  new          
 Priority:  medium         |   Milestone:  PostGIS 2.1.5
Component:  documentation  |     Version:  2.1.x        
 Keywords:                 |  
---------------------------+------------------------------------------------
Description changed by robe:

Old description:

> As noted by someone on IRC, if you upgrade PostGIS from 2.something to
> 2.1 and forget to rerun the legacy.sql script (only applies if you ran it
> in first place),
>
> You may get:
>
> {{{
> Thing is, spatial queries still report this: ERROR: could not access file
> "$libdir/postgis-2.0": No such file or directory
> }}}
>
> I've also seen the dreaded backend error caused by two versions of
> PostGIS running in same db with same set of GUCs fighting for each other.
> The other error (can't remember what it is), happens if postgis-2.0 is
> still present (then you have the unpleasant situation of 2 instances of
> PostGIS running)
>
> I'm hoping in 2.2 that we can get rid of all references to $libdir in the
> legacy scripts, but fair there may be a couple we can't get rid of.

New description:

 As noted by someone on IRC, if you upgrade PostGIS from 2.something to 2.1
 and forget to rerun the legacy.sql script (only applies if you ran it in
 first place),

 You may get:


 Thing is, spatial queries still report this:

 {{{ERROR: could not access file "$libdir/postgis-2.0": No such file or
 directory
 }}}

 I've also seen the dreaded backend error caused by two versions of PostGIS
 running in same db with same set of GUCs fighting for each other.  The
 other error (can't remember what it is), happens if postgis-2.0 is still
 present (then you have the unpleasant situation of 2 instances of PostGIS
 running)

 I'm hoping in 2.2 that we can get rid of all references to $libdir in the
 legacy scripts, but fair there may be a couple we can't get rid of.

--

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2960#comment:1>
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.