On Fri, Sep 3, 2010 at 13:48, Heikki Linnakangas
> On 03/09/10 14:28, Dave Page wrote:
>> On Fri, Sep 3, 2010 at 12:19 PM, Heikki Linnakangas
>> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>>> Here's a WIP patch. It adds a new "TAKE_BACKUP" command to the
>>> 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
>>> 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
> Ok. Another obvious thing that people will want is to gzip the tar file
> while sending it, to reduce network traffic.
Not necessarily obvious, needs to be configurable. There are a lot of
cases where you might not want it.
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2010-09-03 11:51:18|
|Subject: Re: Cost estimates for parameterized paths|
|Previous:||From: Heikki Linnakangas||Date: 2010-09-03 11:48:55|
|Subject: Re: Streaming a base backup from master|