pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Caleb Cushing <xenoterracide@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_dump formatting
Date: Sun, 22 Mar 2009 00:26:02 -0400
Message-ID: <81bfc67a0903212126g7377d7e4i55736a663bccf0dc@mail.gmail.com> (raw)
In-Reply-To: <15202.1237611487@sss.pgh.pa.us>
References: <81bfc67a0903192135v1caa41abtd4618f3df0642834@mail.gmail.com>
	<200903201431.n2KEVZj04033@momjian.us>
	<81bfc67a0903201247l3ddabf14p3e7d2bfd9206cfe7@mail.gmail.com>
	<15202.1237611487@sss.pgh.pa.us>

On Sat, Mar 21, 2009 at 12:58 AM, Tom Lane <tgl@sss.pgh.pa.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



view thread (8+ messages)  latest in thread

Message-ID: <81bfc67a0903212126g7377d7e4i55736a663bccf0dc@mail.gmail.com>
Permalink:  ../81bfc67a0903212126g7377d7e4i55736a663bccf0dc@mail.gmail.com/
Also on:    postgresql.org/message-id/81bfc67a0903212126g7377d7e4i55736a663bccf0dc@mail.gmail.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: xenoterracide@gmail.com, tgl@sss.pgh.pa.us, bruce@momjian.us
  Subject: Re: pg_dump formatting
  In-Reply-To: <81bfc67a0903212126g7377d7e4i55736a663bccf0dc@mail.gmail.com>
  References: <81bfc67a0903192135v1caa41abtd4618f3df0642834@mail.gmail.com> <200903201431.n2KEVZj04033@momjian.us> <81bfc67a0903201247l3ddabf14p3e7d2bfd9206cfe7@mail.gmail.com> <15202.1237611487@sss.pgh.pa.us> <81bfc67a0903212126g7377d7e4i55736a663bccf0dc@mail.gmail.com>

* 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