| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joel Jacobson <joel(at)gluefinance(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_dump --split patch |
| Date: | 2010-12-28 16:51:00 |
| Message-ID: | 6295.1293555060@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joel Jacobson <joel(at)gluefinance(dot)com> writes:
> 2010/12/28 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>> Joel Jacobson <joel(at)gluefinance(dot)com> writes:
>>> Solution: I propose a new option to pg_dump, --split, which dumps each
>>> object to a separate file in a user friendly directory structure:
>>
>> Um ... how does that solve the claimed problem exactly?
> Because then you can do,
> $ diff -r <old schema dump dir> <new schema dump dir>,
> instead of,
> $ diff <old entire schema dump> <new entire schema dump>
> which will nicely reveal each individual object modified, as opposed to a
> huge global diff of everything
That has at least as many failure modes as the other representation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2010-12-28 16:55:19 | Re: knngist - 0.8 |
| Previous Message | Gurjeet Singh | 2010-12-28 16:50:24 | Re: pg_primary_conninfo |