In-Reply-To: <1109875028.12428.98.camel@boomerang.ran.sandia.gov>
References: <1109808921.12430.75.camel@boomerang.ran.sandia.gov>
	<42272D27.4030900@logix-tt.com>
	<1109875028.12428.98.camel@boomerang.ran.sandia.gov>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <659c8c4acbee32e7334c8ff68c97dcba@mail.nih.gov>
Content-Transfer-Encoding: 7bit
Cc: "Markus Schaber" <schabi@logix-tt.com>, pgsql-sql@postgresql.org
From: Sean Davis <sdavis2@mail.nih.gov>
Subject: Re: Building a database from a flat file
Date: Thu, 3 Mar 2005 14:30:27 -0500
To: "Casey T. Deccio" <ctdecci@sandia.gov>


On Mar 3, 2005, at 1:37 PM, Casey T. Deccio wrote:

> On Thu, 2005-03-03 at 08:28 -0700, Markus Schaber wrote:
>> - Create the new date in another schema, and then simply rename those
>> two schemas for "switch over"
>>
>
> This worked very well.  I created another schema ("build") and 
> populated
> the tables within build.  Then:
>
> BEGIN;
> ALTER SCHEMA public RENAME TO public_old;
> ALTER SCHEMA build RENAME TO public;
> COMMIT;
> /* remove data from tables in build schema... */
>
> It was very quick and seamless.
>
> Question: is there an "easy" way to duplicate an existing schema
> (tables, functions, sequences, etc.)--not the data; only the schema?
> This way, I would only need to modify one schema (public) to make
> changes, and the build schema could be created each time as a duplicate
> of the public schema.  Maintenance would be much simpler.

Why not just create a dump of your schema (without data), drop the 
schema, rebuild it from the dump and then populate as normal.  Then do 
the name switch.

Sean