Re: pg_dump --split patch - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump --split patch
Date
Msg-id 3465.1293553592@sss.pgh.pa.us
Whole thread Raw
In response to pg_dump --split patch  (Joel Jacobson <joel@gluefinance.com>)
Responses Re: pg_dump --split patch  (Joel Jacobson <joel@gluefinance.com>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: knngist - 0.8
Next
From: Guillaume Lelarge
Date:
Subject: Re: pg_primary_conninfo