[postgis-users] hard upgrade from 1.5

Sandro Santilli strk at kbt.io
Mon Jan 10 16:18:27 PST 2022

On Mon, Jan 10, 2022 at 10:18:34AM -0800, Paul Ramsey wrote:
> > On Jan 10, 2022, at 10:01 AM, Nathan Wagner <nw at hydaspes.if.org> wrote:
> > So, why exactly is a hard upgrade needed from 1.5 to 2.5?
> Because the pg_dump, pre-2.0 would include all the function definitions

I think the correct answere here is: because the internal
representation of GEOMETRY type changed. That's really the only reason
why one would *need* the "hard upgrade" procedure.

Dropping old functions should be handled just fine by "soft upgrade"
procedure. Filtering out all the function definition is ONLY needed
during an "hard upgrade" of a database in which PostGIS was enabled
via the enabler script (postgis.sql) rather than the CREATE EXTENSION

Out of curiosity: since you're going to copy the data, why do you stop
at 2.5 rather than going straight to 3.x ?


  Libre GIS consultant/developer

More information about the postgis-users mailing list