Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id F41966339AF for ; Fri, 20 Mar 2009 16:47:26 -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 66190-10 for ; Fri, 20 Mar 2009 16:47:21 -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 BC9A56335CF for ; Fri, 20 Mar 2009 16:47:24 -0300 (ADT) Received: by qw-out-2122.google.com with SMTP id 8so574504qwh.61 for ; Fri, 20 Mar 2009 12:47:23 -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=lSCAeI7xJdoJxvnwopst10wRQdPczVSBN0PFEjYEW+0=; b=l3WlhHcmrQrk/Ahzxh5dWqH39WXfhM4HxgVUz51Brvm3pwyPx+t0AeERBwPcfG9FPQ K2D+tMWygV9VTQfv/jlf0pp6nEvKEGwF2WktLi0nFuw4yMiXLN8ukfin49BXfy8TT3bU bSMkxkw05y4aFm6jWLTEcHxepvG9zf5b/RIV4= 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=P4eBXZX3s5LYPTC5+TT+yM394hUcakACURbrGApPnrM+l83oq9ZPvcbCLutr82GTli 6Ge3JwdkjimeB8BuY80Uzh9xHvN4r+bYq/Cf4hdPDJIK8PLZlwWDknL4482k6IHj99e+ LviW2qC2SurDtrvcLF2NrdJ7n7L0lHKB5c6Xo= MIME-Version: 1.0 Received: by 10.229.79.8 with SMTP id n8mr2431527qck.37.1237578436199; Fri, 20 Mar 2009 12:47:16 -0700 (PDT) In-Reply-To: <200903201431.n2KEVZj04033@momjian.us> References: <81bfc67a0903192135v1caa41abtd4618f3df0642834@mail.gmail.com> <200903201431.n2KEVZj04033@momjian.us> Date: Fri, 20 Mar 2009 15:47:16 -0400 Message-ID: <81bfc67a0903201247l3ddabf14p3e7d2bfd9206cfe7@mail.gmail.com> Subject: Re: pg_dump formatting From: Caleb Cushing To: Bruce Momjian Cc: 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/205 X-Sequence-Number: 31705 On Fri, Mar 20, 2009 at 10:31 AM, Bruce Momjian wrote: > > No, but there are database comparison tools to do that, pgdiff being one > of them: after reading a bit on it (docs seem a bit light but I also looked at the mysql one), I don't think it solves my problem at all. it solves a similar one. the way it reads suggests I have access to both databases, I don't. I only have access to 1 (set up on my box from the dump) and the dump from the other. at work we dump our databases and add them to the git repository. and pass the source back and forth, (I think it's a bit inefficient, but I'm not the boss). the problem is 2 fold, 1 it's impossible to get a human readable dump diff, 2 the same reason is going to 'cause the git repository to get large than it should because it stores blobs and these long lines would each end up as a blob even though the character difference might be like 1 character. I suppose I could write a regex script that reformats the dump, personally that scares me a bit. it'd be great if pg could have the option to dump in a more 'diff-able' way. -- Caleb Cushing http://xenoterracide.blogspot.com