I came across this thread from a web search when looking for prior art.
I'm reviving it to alert other interested folks to a flaw in the
provided patch should they try to use it. The feature request seems
somewhat common on the web, and the patch here would cause some fun
debugging sessions otherw
:
> From: Peter Eisentraut
> Subject: Re: [HACKERS] [PATCH] Add --ordered option to pg_dump
> To: "Bob Lunney"
> Cc: pgsql-hackers@postgresql.org
> Date: Thursday, April 15, 2010, 4:36 PM
> On tor, 2010-04-15 at 10:48 -0700,
> Bob Lunney wrote:
> > I needed a
Peter Eisentraut wrote:
On tor, 2010-04-15 at 10:48 -0700, Bob Lunney wrote:
I needed a way to run diffs on two
database dumps to see what data developers put in their
local databases versus the initial database load.
Maybe pg_comparator would help you?
Or DBIx::Compare if you li
On tor, 2010-04-15 at 10:48 -0700, Bob Lunney wrote:
> I needed a way to run diffs on two
> database dumps to see what data developers put in their
> local databases versus the initial database load.
Maybe pg_comparator would help you?
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postg
I needed a way to run diffs on two
database dumps to see what data developers put in their
local databases versus the initial database load. The
pg_dump utility with --inserts works well for this, but
since the order in which the data is returned of the server
is not guaranteed I hacked this patch
