[postgis-users] Re: Upgrade 1.2.1 to 1.3.1 - Problems
mark.cave-ayland at ilande.co.uk
Mon Oct 22 04:04:09 PDT 2007
On Fri, 2007-10-19 at 00:48 -0700, Brian Hamlin wrote:
> My worst problem it seems is that I had expected the clear warnings as
> described in the README and doc.
> I just tried a freshly created DB, initialized with postgis 1.3.1 and
> got none of those terrible errors.
> So things are able to work. It looks like I will have to 'hard
> upgrade' the three of four DBs I have so far..
> I notice that in the 1.3.2 that has appeared they say "make install may
> not work so be prepared to copy the libraries yourself" !! Perhaps they
> meant really to say
> "ifeq ($(PORTNAME), darwin) copy the libs yourself"
> thanks for your patience
Yes. It's probably because the SQL functions contain the "full" path to
the database. As you mention, the easiest solution is probably just to
restore selected tables back into a new PostGIS database. It should help
to remove the version numbers from the lwpostgis.sql as recommended by
Tom on the -devel list, but no-one has gotten around to solving this
ILande - Open Source Consultancy
More information about the postgis-users