From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
Cc: | The Hermit Hacker <scrappy(at)hub(dot)org>, "Ansley, Michael" <Michael(dot)Ansley(at)intec(dot)co(dot)za>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Contributing |
Date: | 1999-07-20 15:42:54 |
Message-ID: | 29746.932485374@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
> The Hermit Hacker wrote:
>> Is this less then when using the -z option for CVS?
> I believe so. I'm just guessing at CVS's behavior, but I *know* that
> CVSup only sends compressed diffs of the changes to update a cvs
> repository or a checked-out tree. afaik CVS sends the entire file,
> compressing it for transmission much as does CVSup.
No, CVS will send either a whole file or a diff (the U or P code in its
printout tells you which way it updated the file, ie, Update whole thing
or Patch). Either way, it's compressed if you've specified -z.
It looks like cvs has some semi-intelligent algorithm for choosing
which to do ... probably, it produces the diff and then looks to see
if the diff is bigger than the file.
I would expect CVSup to require more total net traffic just because
it has to transfer more info --- log entries, intermediate versions
(with CVS, if foo.c has been checked in three times since your last
update, you are sent one diff covering all the changes), etc.
I have not tried to time it however. In any case, I suspect other
considerations are going to drive each hacker's choice of which way
to run.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ansley, Michael | 1999-07-20 15:50:51 | RE: [HACKERS] psql & query string length |
Previous Message | Tom Lane | 1999-07-20 15:31:58 | Re: [HACKERS] selectivity calculation for or_clause is wrong ? |