On Wed, Feb 24, 2010 at 1:49 A= M, I=F1igo Martinez Lasala <imartinez@vectorsf.com> wrote:

To avoid contraints you have to use =96disable-triggers flag during restore. T= hat is done in step 5.

=A0

In order to modify schema you have to locate what is failing. So, first restor= e old schema without modifications in your new database, watch for errors and fix them.

For example:

psql -U username -d database -h server_destination -f schema.sql 2>import_error.log

=A0

You=92ll find all import errors in import_error.log. Since you are only going to lau= nch an schema definition, It will only take a few seconds, so test all you need= .

After locating errors, open schema.sql with your favorite editor and fix them. Th= ere are minor changes between postgresql versions and you=92ll probably have no problems in order to fix them, or ask here if you have many problems.

Once fixed, you will have your new modified_schema.sql and you can proceed with steps 4 and 5.

=A0

Obviously, if errors are related to indexes, functions, broken dependencies, etc witho= ut touching table definitions, everything will go well. However if you have to modify t= able definitions, you will probably not be able to import data in that new schem= a and it will be necesary to look for a new strategy.

=A0

De: Net Tree Inc. [mailto:nettreein= c@gmail.com]
Enviado el: martes, 23 de febrero de 2010 17:36
Para: I=F1igo Martinez Lasala
CC: = pgsql-admin@postgresql.org; pgsql-general@postgresql.org
Asunto: Re: [ADMIN] how do I do dump and restore without bugging wit= h constraint?

=A0

Thanks. Is it by doin= g these steps I can avoid constrain restriction? for step 3, how should I modify th= e schema? and which schema? the target DB's schema that I am trying to du= mp 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=F1igo Martinez La= sala <imarti= nez@vectorsf.com> wrote:

Using pg_dump from your new host (that is, newer ver= sion)

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. <nettreeinc@gmail.com><= br> To: = pgsql-admin@postgresql.org, pgsql-gen= eral@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 o= ne. 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 for= ces data dump to where it suppose to belong?=A0

--
---------------------------------------
Steven Huang