From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
---|---|
To: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com> |
Cc: | "[ADMIN]" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: rsync and streaming replication |
Date: | 2011-11-15 14:08:08 |
Message-ID: | 39A965E0-DE37-41F3-8D69-321419BB8B09@elevated-dev.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Nov 15, 2011, at 3:02 AM, Cédric Villemain wrote:
> no, you are wrong.
> -c, --checksum
> "This changes the way rsync checks if the files have been changed and
> are in need of a transfer. Without this option, rsync uses a "quick
> check" that (by default) checks if each file's size and time of last
> modification match between the sender and receiver. This option
> changes this to compare a 128-bit checksum for each file that has a
> matching size. Generating the checksums means that both sides will
> expend a lot of disk I/O reading all the data in the files in the
> transfer (and this is prior to any reading that will be done to
> transfer changed files), so this can slow things down significantly. "
Seriously, read that and what I said. They are the same, except that the documentation provides more detail.
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
(303) 722-0567 voice
From | Date | Subject | |
---|---|---|---|
Next Message | Cédric Villemain | 2011-11-15 15:30:58 | Re: rsync and streaming replication |
Previous Message | MirrorX | 2011-11-15 10:46:43 | cancelled queries on standby |