From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | guillermo(dot)narvaja(at)fierro-soft(dot)com(dot)ar |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump custom format specification |
Date: | 2012-01-21 13:08:44 |
Message-ID: | 4F1AB8DC.3020103@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 01/21/2012 07:44 AM, Guillermo M. Narvaja wrote:
> Someone has some kind of specification or description of the pg_dump
> custom format?
>
> What I'm trying to do is an utility to remotelly syncronize postgresql
> dumps, using lib_rsync to syncronize each table independently and
> copying blobs only when sizes differ.
>
> I've made the same using the Tar format, but I think most of the
> features and optimizations like paralell-restore are now only available
> with the custom format.
>
> I will do the script in Python, so, I need to know how to parse and
> write pg_dumps in custom format.
You might find this useful: <https://gist.github.com/1258232> It's a
perl script that parses and prints out the header and TOC of a custom
format dump.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-01-21 13:57:45 | Re: CLOG contention, part 2 |
Previous Message | Guillermo M. Narvaja | 2012-01-21 12:44:38 | pg_dump custom format specification |