#2680 closed enhancement (fixed)
In place major version upgrade
| Reported by: | jordanhagan | Owned by: | pramsey |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS Fund Me |
| Component: | postgis | Version: | 2.1.x |
| Keywords: | Cc: |
Description
I'm currently working through upgrading a PostgreSQL 9.0 instance to 9.2 along with PostGIS 1.5.2 → 2.0.2.
Our database is about 2TB in size, so a dump/import upgrade is not feasible for us. Fortunately, only a small portion of our data (5%) is geospatial, so I've been able to put together a procedure where I strip out the geospatial data, uninstall postgis, perform an in place pg_upgrade and then merge the data back in again.
It would be great however if there was a upgrade path available without having to dump/import, as in the future as our geospatial data grows this current procedure will become less and less viable.
I found the following discussion in the mailing list about this issue:
Change History (4)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
I wasn't too clear in my original post, sorry - this was more of a feature request for future upgrades, i.e. 3.0 as you mentioned. It's nice to know that it's a fair way out, though that means that this procedure would surely not work for us by that point. I expect we will have significantly more geospatial data by then.
That said, I'm sure there are at least a few other users who would like to see something like this for 1.5.
Looking forward to a comment from pramsey, thanks for getting back to me so quickly.
comment:3 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
One thing the new serialization (2.0) included was a few bits for version information. So if for some reason we ever do want to change it again (I think robe is probably far too pessimistic on 5 years, I think more like "probably never") we can probably retain the ability to read the old format and write out the new one, effectively doing an in-place upgrade. But hopefully never.
Unfortunately I don't think this is feasible. That comment was made I think before we made so many on disk changes. Also as time goes by fewer and fewer 1.5 users so less of incentive to invest in effort.
PostGIS 2.0-2.* should always be soft upgradeable until will get to PostGIS 3.0 which probably won't be for another 5 years or more.
I'll let pramsey comment.