From: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-admin@postgresql.org
Cc: Caleb Cushing <xenoterracide@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>
Subject: Re: pg_dump formatting
Date: Sun, 22 Mar 2009 10:10:43 +0200
Message-ID: <200903221010.44907.peter_e@gmx.net> (raw)
In-Reply-To: <81bfc67a0903212126g7377d7e4i55736a663bccf0dc@mail.gmail.com>
References: <81bfc67a0903192135v1caa41abtd4618f3df0642834@mail.gmail.com>
<15202.1237611487@sss.pgh.pa.us>
<81bfc67a0903212126g7377d7e4i55736a663bccf0dc@mail.gmail.com>
On Sunday 22 March 2009 06:26:02 Caleb Cushing wrote:
> COPY blarg (blah, bleh, blerg) FROM stdin;
> 1 random character data
> djfa;djjf;sdjl;afkjeoiuoiejk,cxjueiojiojeef98hkjdyf98y92hvniay8syfkdnf38932
>hrhf9e83uifnskjjjjjj3h9r83hhjnnn2iyfhkjsndfi7y938hnksu879hf089h3n299ssdjfh92
>3
>
> the above in pg_dump is one line
>
> it'd be easier to diff if it were say on 3, or best yet with the
> exception of say, binary data or things that can't be wrapped, have
> the data (for like text records) wrapped at 79 characters or maybe 78
> with \ at the end or something...
Maybe wdiff will do what you want.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: peter_e@gmx.net, xenoterracide@gmail.com, tgl@sss.pgh.pa.us, bruce@momjian.us
Subject: Re: pg_dump formatting
In-Reply-To: <200903221010.44907.peter_e@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox