| From: | Nabil Sayegh <nsmail(at)sayegh(dot)de> |
|---|---|
| To: | Joel Burton <jburton(at)scw(dot)org> |
| Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: pg_dump ORDER BY |
| Date: | 2000-12-07 23:20:59 |
| Message-ID: | 3A301B5B.A357356E@sayegh.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Joel Burton wrote:
> If you have databases (db1 and db2) and two tables in each
> (t1 and t2), I think it would be easiest to dump each table
> independently (pg_dump -t t1 d1 > /tmp/d1t1) and diff that to its
> sister table.
>
> You could pretty easily turn diff into COPY input.
>
> If you do a full pg_dump of the database, you'll get non-data stuff,
> like all of the sequences, index declarations, etc. (Unless *that's*
> what you want to reconcile.)
Hm, as both databases are of the same structure, this shouldn't be a
problem.
My problem is that updated rows in a table will appear at the bottom of
the
table if not ordered. That leads to falsealarms of diff :(
cu
--
Nabil Sayegh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Hammonds | 2000-12-07 23:48:19 | Re: Install order |
| Previous Message | Mike Hammonds | 2000-12-07 21:53:28 | Install order |