You haven’t really provided any clues to your underlying problem. What platform you’re on, how your postgis is installed (packages? source?), what the errors you see actually ARE. We don’t publish broken software and then hide the top secret directions for correct use. So when you see things broken, consider it an exceptional condition and gather all the clues you can to share and aid in the process of getting help, otherwise… you won’t get help.
P > On May 16, 2019, at 8:09 AM, Zwettler Markus (OIZ) > <[email protected]> wrote: > > Hi, > > > We did a default PostGIS installation within a PostgreSQL 9.6 database: > > === > create extension if not exists postgis; > create extension if not exists postgis_topology; > create extension if not exists ogr_fdw; > create extension if not exists pgrouting; > === > > This installed PostGIS within the public schema of the database. > (SET SCHEMA is not supported since V2.3 anymore) > > Our customer application was also installed within the public schema. > > When we pg_dump + pg_restore the database we got a lot of errors. > > We tried to pg_restore the dump into a database without postgis extension => > postgis errors > We tried to pg_restore the dump into a database with postgis extension => > postgis errors > We tried to pg_restore only the public schema into a database with postgis > extension => postgis errors > > QUESTION: > How does the PostGIS extension have to be installed so that pg_dump + > pg_restore DO NOT error out? > > > Thanks, > Markus > > _______________________________________________ > postgis-users mailing list > [email protected] <mailto:[email protected]> > https://lists.osgeo.org/mailman/listinfo/postgis-users > <https://lists.osgeo.org/mailman/listinfo/postgis-users>
_______________________________________________ postgis-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/postgis-users
