Skip site navigation (1) Skip section navigation (2)

Re: pg_dump formatting

From: Caleb Cushing <xenoterracide(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_dump formatting
Date: 2009-03-22 04:26:02
Message-ID: 81bfc67a0903212126g7377d7e4i55736a663bccf0dc@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Sat, Mar 21, 2009 at 12:58 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> What exactly do you find un-diffable about it?

after doing a bit of testing to be more explicit... pg isn't half as
bad as mysql, so I've mostly been asking about something that doesn't
apply...

however, it seems that it creates 1 line per row, and although this is
much better than mysql's behavior. for larger tables or fields this
would still be a bit harder to diff.


COPY blarg (blah, bleh, blerg) FROM stdin;
1       random character data
djfa;djjf;sdjl;afkjeoiuoiejk,cxjueiojiojeef98hkjdyf98y92hvniay8syfkdnf38932hrhf9e83uifnskjjjjjj3h9r83hhjnnn2iyfhkjsndfi7y938hnksu879hf089h3n299ssdjfh923

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...

mysql is much more abysmal, and I believe it puts the entire table on
one line... or some such insanity.
-- 
Caleb Cushing

http://xenoterracide.blogspot.com

In response to

Responses

pgsql-admin by date

Next:From: Peter EisentrautDate: 2009-03-22 08:10:43
Subject: Re: pg_dump formatting
Previous:From: Tena SakaiDate: 2009-03-21 21:48:34
Subject: Re: vacuuming and reindexing

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group