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

From Tom Lane
Subject Re: pg_dump --split patch
Date
Msg-id 12681.1293582297@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump --split patch  (David Wilson <david.t.wilson@gmail.com>)
Responses Re: pg_dump --split patch  (Joel Jacobson <joel@gluefinance.com>)
List pgsql-hackers
David Wilson <david.t.wilson@gmail.com> writes:
> On Tue, Dec 28, 2010 at 2:39 PM, Joel Jacobson <joel@gluefinance.com> wrote:
>> I didn't include the arguments in the file name, as it would lead to very
>> long file names unless truncated, and since the problem is very limited, I
>> think we shouldn't include it. It's cleaner with just the name part of the
>> tag in the file name.

> Why not place all overloads of a function within the same file? Then,
> assuming you order them deterministically within that file, we sidestep the
> file naming issue and maintain useful diff capabilities, since a diff of the
> function's file will show additions or removals of various overloaded
> versions.

If you've solved the deterministic-ordering problem, then this entire
patch is quite useless.  You can just run a normal dump and diff it.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: SSI SLRU strategy choices
Next
From: Tom Lane
Date:
Subject: Re: Revised patches to add table function support to PL/Tcl (TODO item)