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, David Wilson <david.t.wilson@gmail.com>, Gurjeet Singh <singh.gurjeet@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2010-12-29T01:51:38Z
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 08:18 PM, Joel Jacobson wrote:
> 2010/12/29 Tom Lane <tgl@sss.pgh.pa.us <mailto:tgl@sss.pgh.pa.us>>
>
>
>     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.
>
>
> No, that's only half true.
>
> Diff will do a good job minimizing the "size" of the diff output, yes, 
> but such a diff is still quite useless if you want to quickly grasp 
> the context of the change.
>
> If you have a hundreds of functions, just looking at the changed 
> source code is not enough to figure out which functions were modified, 
> unless you have the brain power to memorize every single line of code 
> and are able to figure out the function name just by looking at the 
> old and new line of codes.
>
>

try:

  diff -F '^CREATE' ...

cheers

andrew