| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "[ADMIN]" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: streaming replication |
| Date: | 2011-11-07 17:19:42 |
| Message-ID: | 8CC5F53E-1D02-43DE-8198-D2BB9297173E@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Nov 7, 2011, at 10:10 AM, Kevin Grittner wrote:
> If the bottleneck is the network, be sure that you are using a
> daemon on the remote side; otherwise you do drag all the data over
> the wire for any file which doesn't have an identical timestamp and
> size. An example of how to do that from the rsync man page:
>
> rsync -av -e "ssh -l ssh-user" rsync-user(at)host::module /dest
>
> This will try to identify matching portions of files and avoid
> sending them over the wire.
??? The normal way of using will using rolling checksums rather than sending all the data over the network:
rsync -av rsync-user(at)host:/source /dest
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-11-07 17:36:03 | Re: streaming replication |
| Previous Message | Kevin Grittner | 2011-11-07 17:16:06 | Re: pg_dump from 8.4 to 8.3 |