On Tue, Jan 11, 2022 at 05:45:16PM +, Nathan Wagner wrote:
> Could this have been done via 'create extension postgis from unpackaged'?
> I think that doesn't work for an in-place upgrade because it can't
> handle converting the internal representation.
You are right: "create extension from
> On Jan 11, 2022, at 9:45 AM, Nathan Wagner wrote:
>
> On Tue, Jan 11, 2022 at 01:18:27AM +0100, Sandro Santilli wrote:
>> On Mon, Jan 10, 2022 at 10:18:34AM -0800, Paul Ramsey wrote:
On Jan 10, 2022, at 10:01 AM, Nathan Wagner wrote:
>>>
So, why exactly is a hard upgrade needed
On Tue, Jan 11, 2022 at 01:18:27AM +0100, Sandro Santilli wrote:
> On Mon, Jan 10, 2022 at 10:18:34AM -0800, Paul Ramsey wrote:
> > > On Jan 10, 2022, at 10:01 AM, Nathan Wagner wrote:
> >
> > > So, why exactly is a hard upgrade needed from 1.5 to 2.5?
> >
> > Because the pg_dump, pre-2.0 would
On Mon, Jan 10, 2022 at 10:18:34AM -0800, Paul Ramsey wrote:
> > On Jan 10, 2022, at 10:01 AM, Nathan Wagner 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:
> On Jan 10, 2022, at 10:01 AM, Nathan Wagner wrote:
>
> I am working on an upgrade from postgis 1.5 on postgresql 9.0 to postgis
> 2.5 on postgresql 11.
>
> The docs say that a hard upgrade is needed. Is that still true if we're
> migrating the data from one database to another? Our
I am working on an upgrade from postgis 1.5 on postgresql 9.0 to postgis
2.5 on postgresql 11.
The docs say that a hard upgrade is needed. Is that still true if we're
migrating the data from one database to another? Our migration strategy
is to do a copy out of the table data (as in a \copy
