Thanks. Is it by doing these steps I can avoid constrain restriction? for step 3, how should I modify the schema? and which schema? the target DB's schema that I am trying to dump the schema and data in? But this is the problem, I am not sure whats different between the two schema's, there are just too many tables to check. What's your tips?
Steven On Tue, Feb 23, 2010 at 7:03 PM, Iñigo Martinez Lasala < imarti...@vectorsf.com> wrote: > Using pg_dump from your new host (that is, newer version) > > 1- Dump schema. > pg_dump -h server_source -U username -s -Fp -f schema.sql database > > 2- Dump data only. > pg_dump -h server_source -U username -a -Fc -f data.dmp database > > 3- Modify schema. > > 4- Restore schema in new host. > psql -U username -d database -h server_destination -f modified_schema.sql > > 5- Restore data disabling triggers > pg_restore -h server_destination -U username -d database --disable-triggers > -a data.dmp > > > > -----Original Message----- > *From*: Net Tree Inc. > <nettree...@gmail.com<%22net%20tree%20inc.%22%20%3cnettree...@gmail.com%3e> > > > *To*: pgsql-ad...@postgresql.org, pgsql-general@postgresql.org > *Subject*: [ADMIN] how do I do dump and restore without bugging with > constraint? > *Date*: Tue, 23 Feb 2010 12:50:27 +0800 > > Hi all, > > I am dumping both schema and data from old database to new one. The new > database schema is somehow contain slightly different schema then the old > one. When I do restore it shown alot errors related with constraints. How > can I dump and to restore from old to new without dealing with constraint > and just forces data dump to where it suppose to belong? > > > > > > > > > > -- --------------------------------------- Steven Huang
