On Fri, Sep 3, 2010 at 2:24 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Fri, Sep 3, 2010 at 7:28 AM, Dave Page <dpage@pgadmin.org> wrote:
>> On Fri, Sep 3, 2010 at 12:19 PM, Heikki Linnakangas
>> <heikki.linnakangas@enterprisedb.com> wrote:
>>> Here's a WIP patch. It adds a new "TAKE_BACKUP" command to the replication
>>> command set. Upon receiving that command, the master starts a COPY, and
>>> streams a tarred copy of the data directory to the client. The patch
>>> includes a simple command-line tool, pg_streambackup, to connect to a server
>>> and request a backup that you can then redirect to a .tar file or pipe to
>>> "tar x".
>>
>> Cool. Can you add a TODO to build in code to un-tar the archive? tar
>> is not usually found on Windows systems, and as we already have tar
>> extraction code in pg_restore it could presumably be added relatively
>> painlessly.
>
> It seems like the elephant in the room here is updating an existing
> backup without recopying the entire data directory. Perhaps that's
> phase two, but worth keeping in mind...
rsync? Might be easier to use that from day 1 (well, day 2) than to
retrofit later.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
