Re: rsync and streaming replication - Mailing list pgsql-admin

From Cédric Villemain
Subject Re: rsync and streaming replication
Date
Msg-id CAF6yO=3WQMsa5WQkHNbfW9URnto5M94U5U9ZEQ3LS=dLRri2dw@mail.gmail.com
Whole thread Raw
In response to Re: rsync and streaming replication  (Scott Ribe <scott_ribe@elevated-dev.com>)
Responses Re: rsync and streaming replication  (Scott Ribe <scott_ribe@elevated-dev.com>)
List pgsql-admin
2011/11/14 Scott Ribe <scott_ribe@elevated-dev.com>:
> On Nov 14, 2011, at 10:59 AM, Jean-Armel Luce wrote:
>
>> just for the value : rsync --checksum is the option to use to prevent
>> copying of identical files
>
> No, that's not what it's used for. It already avoids sending identical blocks by using checksums. --checksum forces a
checksumon files that have identical sizes & mod times, thus catching files that have different contents despite having
thesame mod times & sizes. 

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. "
...


--
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Développement, Expertise et Formation

pgsql-admin by date:

Previous
From: Alexander Burbello
Date:
Subject: Restore db
Next
From: MirrorX
Date:
Subject: cancelled queries on standby