| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Dave Page <dpage(at)pgadmin(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Streaming a base backup from master |
| Date: | 2010-09-03 16:22:06 |
| Message-ID: | 4C8120AE.3030503@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/09/10 19:09, Stephen Frost wrote:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>> IOW, what I'd like to see is protocol extensions that allow an external
>> copy of rsync to be invoked; not build in rsync, or tar, or anything
>> else that we could get off-the-shelf.
>
> I'd much rather use an existing library to implement it than call out to
> some external utility. That said, I'm about as thrilled with libtar as
> librsync after a bit of googling around. :/
The code to build a tar archive is about 200 lines of code. The amount
of code for untar is about the same. That's about the amount of effort
We could add zlib compression since we already link with that, but
that's about it. I'm not interested in adding more infrastructure for
more tools. For more complicated scenarios, you can still use
pg_start/stop_backup() as usual, there's nothing wrong with that.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-09-03 16:23:20 | Re: Streaming a base backup from master |
| Previous Message | Kevin Grittner | 2010-09-03 16:11:34 | Re: Streaming a base backup from master |