Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Problem with mirrorring
Date: Sun, 3 Oct 2004 11:17:22 +0100
Message-ID: 
 <E7F85A1B5FF8D44C8A1AF6885BC9A0E407B40D@ratbert.vale-housing.co.uk>
Thread-Topic: [pgsql-www] Problem with mirrorring
Thread-Index: AcSotQV0TK7xQieeRaS3d6HdK6we0AAAwVewAA1msAAAESGb7g==
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "John Hansen" <john@geeknet.com.au>,
	"Devrim GUNDUZ" <devrim@gunduz.org>
Cc: "PostgreSQL WWW Mailing List" <pgsql-www@postgresql.org>


-----Original Message-----
From: John Hansen [mailto:john@geeknet.com.au]
Sent: Sun 10/3/2004 3:10 AM
To: Dave Page; Devrim GUNDUZ
Cc: PostgreSQL WWW Mailing List
Subject: RE: [pgsql-www] Problem with mirrorring

> Don't you mean quite efficient... ?

No, quite inefficient. We rebuild every file on the site regardless of whet=
her something has changed, hence every time rsync runs it sees a modified f=
ile. What I had completely forgotten when I wrote that (and later noted whe=
n I remembered) is that rsync only transfers a diff of each files, so thing=
s aren't really that bad.

Of course, how it does that is a mystery to me - without fully comparing bo=
th versions, how can it create a diff? I guess that's what made it PhD mate=
rial...

/D