To: Peter Eisentraut <peter_e@gmx.net>
cc: pgsql-admin@postgresql.org, Caleb Cushing <xenoterracide@gmail.com>,
	Bruce Momjian <bruce@momjian.us>
Subject: Re: pg_dump formatting 
In-reply-to: <200903221010.44907.peter_e@gmx.net> 
References: <81bfc67a0903192135v1caa41abtd4618f3df0642834@mail.gmail.com>
	<15202.1237611487@sss.pgh.pa.us>
	<81bfc67a0903212126g7377d7e4i55736a663bccf0dc@mail.gmail.com>
	<200903221010.44907.peter_e@gmx.net>
Comments: In-reply-to Peter Eisentraut <peter_e@gmx.net>
	message dated "Sun, 22 Mar 2009 10:10:43 +0200"
Date: Sun, 22 Mar 2009 10:44:00 -0400
Message-ID: <11595.1237733040@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Peter Eisentraut <peter_e@gmx.net> writes:
> 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.

I don't think we'd consider making the kind of changes to the COPY
specification that would be needed to allow this sort of thing in COPY
mode.  However, it'd be pretty trivial to put \n instead of space
between fields in the INSERT dump formats.  I wonder whether that would
answer the need ...

			regards, tom lane