From: Net Tree Inc. <nettreeinc@gmail.com>
To: John R Pierce <pierce@hogranch.com>
Cc: pgsql-general@postgresql.org
Subject: Re: how do I do dump and restore without bugging with constraint?
Date: Tue, 23 Feb 2010 14:39:11 +0800
Message-ID: <bd9689741002222239y5626a661i2162aed9888e9cfb@mail.gmail.com> (raw)
In-Reply-To: <4B836324.7090604@hogranch.com>
References: <bd9689741002222050r1b782543rad955f64e46630ce@mail.gmail.com>
<4B836324.7090604@hogranch.com>
Ok, I am just trying to find the proper way to back and restore database
that contain restriction.
The other way to ask. If I have two 99% schema similar databases. The old
one might contain few columns that does not exist in the new one and contain
constrains that the new DB does not have. In that case, what's standard to
do this?
Since they are 99% similar in schema, can I do "data dump" only ? will that
work?
If owner for database between Old and new DB are different, do I must add
that owner in by create new role?
appreciated,
Steven
On Tue, Feb 23, 2010 at 1:09 PM, John R Pierce <pierce@hogranch.com> wrote:
> Net Tree Inc. wrote:
>
>> 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?
>>
>>
>>
>>
>
> if you're dumping the schema and the data, you should be restoring into an
> empty database, not into an existing database.
>
>
>
--
---------------------------------------
Steven Huang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: nettreeinc@gmail.com, pierce@hogranch.com, pgsql-general@postgresql.org
Subject: Re: how do I do dump and restore without bugging with constraint?
In-Reply-To: <bd9689741002222239y5626a661i2162aed9888e9cfb@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox