| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, ik(at)postgresql-consulting(dot)com |
| Cc: | Claudio Freire <klaussfreire(at)gmail(dot)com>, David Johnston <polobo(at)yahoo(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: pg_dump vs pg_basebackup |
| Date: | 2014-03-25 15:55:18 |
| Message-ID: | 5331A6E6.8010503@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 03/25/2014 08:21 AM, Magnus Hagander wrote:
> I would say that's the one thing that rsync is *not*. pg_basebackup
> takes care of a lot of things under the hood. rsync is a lot more
> complicated, in particular in failure scenarios, since you have to
> manually deal with pg_start/stop_backup().
>
> There are definitely reasons you'd prefer rsync over pg_basebackup, but
> I don't believe simplicity is one of them.
>
> //Magnus
Good God man... since when do you top post!
Well there are tools that use rsync to solve those issues :P. We even
have one that does multi-threaded rsync so you can pull many Terabytes
in very little time (relatively).
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
Political Correctness is for cowards.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alan Hodgson | 2014-03-25 16:12:46 | Re: pg_dump vs pg_basebackup |
| Previous Message | Graeme B. Bell | 2014-03-25 15:48:07 | Re: pg_dump vs pg_basebackup |