[postgis-users] Errors upgrading from 1.4.0 to 1.5.2

David Cato otac at crunchyfrog.net
Sun Oct 31 22:13:33 PDT 2010


Paragon Corporation wrote ...

> My guess is that you probably have some sql functions using the old
> deprecated Extent aggregate so it can't be cleanly dropped and unfortunately
> there is no ALTER AGGREGATE function in PostgreSQL yet.
> 
> What you can do is one of 3 things that come to mind
> 
> 1) Find the code and change it to use ST_Extent.  This is probalby in an SQL
> function since PostgreSQL is not smart enough in 8.4 to check the internals
> of plpgsql.  If you are using pgAdminIII it shows
> The dependents of each function in one of the tabs..
> 
> 2) Do a Hard upgrade -- by that I mean what Paul has described here -
> http://blog.cleverelephant.ca/2010/09/postgis-back-up-restore.html
> 
> Or 
> 3) If your database is too big to go thru that trouble
> 
> Just remark out the DROP/CREATE AGGREGATE of the deprecated functions. And
> hmm deal with it later.  Those will still work anyway.
> 
> If you get an error with ST_Extent  (I actually don't think that has changed
> signature between 1.4 and 1.5 so you can probably safely remark that out
> too.)

Thanks for the quick reply.

I couldn't find anything that was using the old Extent aggregate so I
opted for the hard upgrade approach and everything seems to be working
fine.

-- 
David Cato




More information about the postgis-users mailing list