On Nov 15, 2011, at 8:30 AM, Cédric Villemain wrote: > Seriously, I did. Is my post "just for the value : rsync --checksum is > the option to use to prevent copying of **identical files**" incorrect > ?
It's at least incomplete and somewhat misleading. But I guess you could say the same about my post; we seem to be focusing on 2 different aspects of its behavior ;-) > OP contains "It looks that all database files do not have the same > modification date in the master node and in the slave nodes, so the > rsync copies quite all the database from the new master to the > slaves." Yes, and rsync should only be copying changed blocks in that case, of which you are aware, but which OP did not seem to realize. > One benefit is when files are in fact identical on both side, so that > rsync does not have to process checksum for each blocks on source and > destination. (when there are few changes, we expect rsync to copy only > those few changes, with or without --checksum). Well, but it does calculate checksums on the entire contents of both files (which takes as much I/O and about as much CPU as calculating checksums for each block), even when timestamps & sizes are identical. For the OP's case, identical files with differing timestamps, the only potential savings is from not exchanging checksums over the network, which is not likely to offer any meaningful improvement in performance, which still leaves open the question as to why rsync is so slow in that, when we know it is usually relatively fast to sync two servers with few differences. Would be nice to actually hear from OP regarding file sizes/counts & network bandwidth & disks & and so on ;-) -- Scott Ribe scott_r...@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
