Re: pg_dump --split patch
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joel Jacobson <joel@gluefinance.com>
Cc: pgsql-hackers@postgresql.org
Date: 2010-12-28T16:26:32Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
pg_dump: Output functions deterministically sorted
- 7b583b20b1c9 9.3.0 cited
-
When sorting functions in pg_dump, break ties (same name) by number of arguments
- 1acc06a1f4ae 9.0.0 cited
Joel Jacobson <joel@gluefinance.com> writes: > Dear fellow hackers, > Problem: A normal diff of two slightly different schema dump files (pg_dump > -s), will not produce a user-friendly diff, as you get all changes in the > same file. > 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? > [-f filename] : main dump file, imports each splitted part using \i > [-f filename]-split/[desc]/[tag]/[oid].sql : dump of the oid This particular choice seems remarkably *un* friendly, since two dumps from different DBs will inevitably not share the same OIDs, making it practically impossible to compare them even if they are logically identical. But even without the choice to use OIDs in the filenames I'm unconvinced that file-per-object is a good idea in any way shape or form. regards, tom lane