Message-ID: <024801c46906$10d87d00$0403a8c0@fejleszt4>
From: "=?iso-8859-2?B?U1rbQ1MgR+Fib3I=?=" <surrano@mailbox.hu>
To: <pgsql-sql@postgresql.org>
References: <GFEPILCFHLAKEKOGANLLCEDLCBAA.verebes@freemail.hu>
	<00a001c4680b$f14c60a0$0403a8c0@fejleszt4>
	<1089636713.58812.37.camel@jester>
	<01f401c468f6$90905c80$0403a8c0@fejleszt4>
	<1089739239.48027.64.camel@jester>
	<022401c46900$b85c26e0$0403a8c0@fejleszt4>
	<1089741816.48027.89.camel@jester>
Subject: Re: Constraint->function dependency and dump in 7.3
Date: Tue, 13 Jul 2004 20:20:24 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: 7bit

Dear Rod,

That sounds as good as simple ;) As for as patching, we do something like
that. Developed a PHP script that compares schema files (not dumps, but
source codes instead) to the actual. Say, it creates a temp table and
compares it to the existing one, examining pg_attributes, pg_indexes,
pg_constraints etc. then runs appropriate ALTER TABLE commands on the old
table. Creating a clean double of the prod and keeping its schema sounds
good to handle exceptional things.

Yours,
G.
%----------------------- cut here -----------------------%
\end

----- Original Message ----- 
From: "Rod Taylor" <pg@rbt.ca>
Sent: Tuesday, July 13, 2004 8:03 PM


> When building a new box to duplicate production:
> 1. Apply all patches in order
> for i in `ls *.sql` ; do cat $i | psql test_db ; done
> 2. Do a data dump of production and restore that to the testing area
> pg_dump --data-only prod_db | psql test_db
>
> Now you don't need to worry about whether the production schema will or
> will not dump properly, since you can reproduce that using external
> files.