Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 2335C632BA0 for ; Sun, 22 Mar 2009 01:26:08 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 63752-07 for ; Sun, 22 Mar 2009 01:26:05 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by mail.postgresql.org (Postfix) with ESMTP id C8F636318F3 for ; Sun, 22 Mar 2009 01:26:03 -0300 (ADT) Received: by qw-out-2122.google.com with SMTP id 8so740923qwh.61 for ; Sat, 21 Mar 2009 21:26:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=8VR9eEbv558RXanyXdDlN9ETWnkhDvSqZ84+3Q1YE1Y=; b=c9hEMslkL+f0Sg9s3toAqNQ4UUsQm1kUvlqidq+OhUPg11FBqbEiqMWh4utBTlZ/Qu H8L8uoEU6ACnTVXK5dTlUc8DiEiShF+hZBwK1Ky/O9YtsKKjCtzbQcO3H6SNlikE7u7M 60D92LKLGusyOyekaRQG1XauvGJkeQYQdF+i0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=WanL6mEiMCWM2Kptty5tpJKo2Xo4oa0kk56CE0twhi0mZqEwqFZ8+Dx+TSn2rmYA0h rs1Wre8u3DIhxSoyvuR2tb5D8D/tBSqlmYpQYfkEzvOmAIikb8Ujm8WrSJD2v1QYYwmd 63pfaTmt/0eC3lrx4MlyF6eZOlMn27ZpRTIVo= MIME-Version: 1.0 Received: by 10.229.79.7 with SMTP id n7mr2647314qck.87.1237695962098; Sat, 21 Mar 2009 21:26:02 -0700 (PDT) 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> Date: Sun, 22 Mar 2009 00:26:02 -0400 Message-ID: <81bfc67a0903212126g7377d7e4i55736a663bccf0dc@mail.gmail.com> Subject: Re: pg_dump formatting From: Caleb Cushing To: Tom Lane Cc: Bruce Momjian , pgsql-admin@postgresql.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200903/212 X-Sequence-Number: 31712 On Sat, Mar 21, 2009 at 12:58 AM, Tom Lane 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