DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=I2Eud9smTyIeEaOJ7gqwb4KG/PpjQUPhnCwaLHS7/KT8vd06hBXmisOvSwsJMBAAs3
	wayKkxIGanoX67YyuqZPx8tLIy5eCYUkky4DLL5yG2o1uKSMU0LLneaNGHKdsSaU0FDM
	hRFWtMirr8jHB2b2kaEqJK8FpnHKWageeXL1s=
MIME-Version: 1.0
In-Reply-To: <bd9689741002222239y5626a661i2162aed9888e9cfb@mail.gmail.com>
References: <bd9689741002222050r1b782543rad955f64e46630ce@mail.gmail.com>
	<4B836324.7090604@hogranch.com>
	<bd9689741002222239y5626a661i2162aed9888e9cfb@mail.gmail.com>
Date: Tue, 23 Feb 2010 00:31:29 -0700
Message-ID: <dcc563d11002222331x74b5ac69nee84096585dad13a@mail.gmail.com>
Subject: Re: how do I do dump and restore without bugging with
	constraint?
From: Scott Marlowe <scott.marlowe@gmail.com>
To: "Net Tree Inc." <nettreeinc@gmail.com>
Cc: John R Pierce <pierce@hogranch.com>, pgsql-general@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 22, 2010 at 11:39 PM, Net Tree Inc. <nettreeinc@gmail.com> wrot=
e:
> 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=A0similar databases. The o=
ld
> one might contain few columns that does not exist in the new one and cont=
ain
> constrains that the new DB does not have. In that case, what's standard t=
o
> do this?
> Since they are 99% similar in schema, can I do "data dump" only ? will th=
at
> work?
> If owner for database between Old and new DB are different, do I must add
> that owner in by create new role?
> appreciated,

What I would do is to dump and restore the db as a whole which will
take care of constraint issues.  Then I would alter the tables to
match the new schema.