[postgis-devel] In-place upgrade to 2.0

Mark Cave-Ayland mark.cave-ayland at siriusit.co.uk
Tue May 31 02:12:41 PDT 2011

On 24/05/11 16:30, Paul Ramsey wrote:

> yes, my scheme was going to be to two-step by first creating
> GEOMETRY2, then altering all the columns to that (by maintaining an
> lwgeom handler to do the cast from serialized_form to gserialized),
> then creating GEOMETRY and altering all the columns to that. Which
> would work fine for data-only databases, but installations with more
> complex constructions (views, triggers) expecting 'geometry' input
> arguments might balk if I alter their column types underneath them.
> P.

GEOMETRY2? That sounds very Oracle-esque... ;)



Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
t: +44 870 608 0063

Sirius Labs: http://www.siriusit.co.uk/labs

More information about the postgis-devel mailing list