Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    Upgrading will be difficult. I think there is no point in upgrading from one EOL version to another EOL (pg12 will be EOL in a few months). I recommend considering upgrading to a newer version than 12. Upgrading will be slow and via dump. I remember in some releases (something like 2.0) upgrading postgis itself was non-trivial. Commented Aug 2, 2024 at 6:30
  • 1
    In the basic scenario, create extension postgis on the new version of the database, migrate the structure of user tables, but do not touch the postgis functions/operators/create type (in 9.0 there was no create extension, so pg_dump will try to dump the entire postgis of the old version and this will not be able to import, as expected), when the script is ready to migrate the database schema without errors - migrate with the data of these tables. Commented Aug 2, 2024 at 6:31
  • @melkij So by doing that, I will be able to move those user tables with the postgis/spatial data types? I'm confused as to why pg_dump/postgis_restore.pl can't already handle that Commented Aug 2, 2024 at 12:53