From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Igor Shevchenko <igor(at)carcass(dot)ath(dot)cx> |
Cc: | btober(at)computer(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: db schema diff |
Date: | 2004-04-12 21:57:12 |
Message-ID: | 14252.1081807032@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Igor Shevchenko <igor(at)carcass(dot)ath(dot)cx> writes:
> On Monday 12 April 2004 22:38, you wrote:
>> ${PG_DUMP} -s -p 5432 mydb|${GREP} -v '^--'|${CAT} -s >5432.sql
>> ${PG_DUMP} -s -p 5433 mydb|${GREP} -v '^--'|${CAT} -s >5433.sql
>> ${PG_DUMP} -s -p 5434 mydb|${GREP} -v '^--'|${CAT} -s >5434.sql
>>
>> ${DIFF} 5432.sql 5433.sql > 5432-5433.diff
>> ${DIFF} 5433.sql 5434.sql > 5433-5434.diff
> I used to do exactly this but the pg_dump order is different on my two
> servers, and this generates lots of false diffs.
FWIW, CVS tip pg_dump has been modified to produce a consistent (and
safe) dump order, so its output should be a lot more useful for schema
diff'ing purposes than previous releases were.
It should work to build a current snapshot and use its pg_dump against
older servers, if you need a solution now.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Browne | 2004-04-12 22:01:00 | Re: PostgreSQL Invalid Page Header in Block XXXXX |
Previous Message | Igor Shevchenko | 2004-04-12 20:21:29 | Re: db schema diff |