The way I do it (learned from others on this list) is to backup the schema(s) with my data in them; I store my data outside the public schema to accommodate this. Works great, especially at upgrade time (not overwriting newer functions). I used PgAdmin to backup a few items from public schema, e.g. added srids, and geometry_columns table from public schema, then saved the resulting script to add that to my backup.
Mark On Tue, Jan 3, 2012 at 11:53 AM, DrYSG <ygutfre...@draper.com> wrote: > > I am running PostGreSQL 9.1 and PostGIS 1.5.4. I backed up a PostGIS database > with PgAdmin III. > > When I restore it I get a lot of error messages about redefinition of > functions. (it backed up all the PostGIS functions and now is restoring them > even though they are already defined, since I templated the new database > from the PostGIS database. > > I would like to cut out these 1,000 or so error messages so I can see what > is actually not working, if anythng. > > I looked and did not see any obvious options in the pgAdmin III restore > dialog. Has anyone done this? > > -- > View this message in context: > http://old.nabble.com/The-correct-way-to-restore-is--tp33073199p33073199.html > Sent from the PostGIS - User mailing list archive at Nabble.com. > > _______________________________________________ > postgis-users mailing list > postgis-users@postgis.refractions.net > http://postgis.refractions.net/mailman/listinfo/postgis-users _______________________________________________ postgis-users mailing list postgis-users@postgis.refractions.net http://postgis.refractions.net/mailman/listinfo/postgis-users
