| From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, John Hansen <john(at)geeknet(dot)com(dot)au>, Devrim GUNDUZ <devrim(at)gunduz(dot)org>, PostgreSQL WWW Mailing List <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Problem with mirrorring |
| Date: | 2004-10-03 14:03:49 |
| Message-ID: | 20041003110250.D96717@ganymede.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Sun, 3 Oct 2004, Peter Eisentraut wrote:
> Dave Page wrote:
>> Of course, how it does that is a mystery to me - without fully
>> comparing both versions, how can it create a diff? I guess that's
>> what made it PhD material...
>
> It doesn't create a diff. It computes checksums for pieces of the file
> and transfers those.
>
> Apparently, though, it first checks the modification time before doing
> all that checksum stuff.
Right, and if you want, you can use the --size-only arg to rsync to
disable the timestamp check and made it only a size check ... so, if the
size doesn't change, the page wasn't actually modified ... and, I can't
think of many situations where if hte file changed, the size wouldn't
change by *at least* one character, but I imagine it could happen ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Hansen | 2004-10-03 23:41:54 | archves.postgresql.org |
| Previous Message | John Hansen | 2004-10-03 11:58:46 | Re: Problem with mirrorring |