Horton

Re: pg_dump --split patch

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Joel Jacobson <joel@gluefinance.com>
Cc: pgsql-hackers@postgresql.org
Date: 2010-12-28T17:17:22Z
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 →

  1. pg_dump: Output functions deterministically sorted

  2. When sorting functions in pg_dump, break ties (same name) by number of arguments


On 12/28/2010 11:59 AM, Joel Jacobson wrote:
> 2010/12/28 Tom Lane <tgl@sss.pgh.pa.us <mailto:tgl@sss.pgh.pa.us>>
>
>
>     That has at least as many failure modes as the other representation.
>
>
> I don't follow, what do you mean with "failure modes"? The oid in the 
> filename? I suggested to use a sequence instead but you didn't comment 
> on that. Are there any other failure modes which could cause a diff -r 
> between two different databases to break?
>
> (This might be a bad idea for some other reason, but I noticed a few 
> other users requesting the same feature when I googled "pg_dump split".)
>
>

A better approach to the problem might be to have a tool which did a 
comparison of structures rather than a textual comparison of dumps. For 
extra credit, such a tool might even try to produce a sync script for 
you ...

Of course, that task might involve more effort than you want to devote 
to it.

cheers

andrew