From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "James B(dot) Byrne" <byrnejb(at)harte-lyne(dot)ca> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Backup using GiT? |
Date: | 2008-06-13 19:51:16 |
Message-ID: | 14754.1213386676@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"James B. Byrne" <byrnejb(at)harte-lyne(dot)ca> writes:
> I have recently had to teach myself how to use git and the thought came to me
> that this tool might provide a fairly low setup cost way of passing pg_dumps
> over the network to our off site data store. Think Rsync, but on a file
> content basis; just the content diff gets transmitted.
Huh? rsync does within-file diff transmission already.
> GiT works by compressing deltas of the contents of successive versions of file
> systems under repository control. It treats binary objects as just another
> object under control. The question is, are successive (compressed) dumps of
> an altered database sufficiently similar to make the deltas small enough to
> warrant this approach?
No. If you compress it, you can be pretty certain that the output will
be different from the first point of difference to the end of the file.
You'd have to work on uncompressed output, which might cost more than
you'd end up saving ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-06-13 19:56:44 | Re: dblink() cursor error/issue (TopMemoryContext) |
Previous Message | Chander Ganesan | 2008-06-13 18:46:20 | Re: Backup using GiT? |