CVS mirror, was Re: [PATCHES] ADD/DROPS INHERIT (actually INHERIT / NO INHERIT) - Mailing list pgsql-hackers

From Andrew Dunstan
Subject CVS mirror, was Re: [PATCHES] ADD/DROPS INHERIT (actually INHERIT / NO INHERIT)
Date
Msg-id 44A932E2.60504@dunslane.net
Whole thread Raw
Responses Re: CVS mirror, was Re: [PATCHES] ADD/DROPS INHERIT (actually INHERIT  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-hackers
[redirecting to -hackers]

context: a buildfarm member apparently failed through getting a partial 
update from CVS, possibly because the anonymous mirror was also 
partially updated.

Tom Lane wrote:

>"Andrew Dunstan" <andrew@dunslane.net> writes:
>  
>
>>Since CVS updates are not atomic, it's hard to see how mirroring could be,
>>unless you did something like disallow updates, mirror, allow updates. I
>>suspect such a cure would be worse than the disease. This is such a rare
>>event that I don't think it's worth the trouble. Buildfarm members are doing
>>200 builds a day or more, and I can't recall having seen this before.
>>    
>>
>
>Yeah, I don't remember having seen it before either, but on the other
>hand I haven't been paying super close attention.
>
>One easy low-tech fix would be for Marc to publish the exact times at
>which the mirror syncs run (I think it might be something like 20 past
>the hour but I'm not sure), and then we could tell buildfarm owners not
>to schedule their CVS pulls to start in that particular five-minute
>window, and committers could try to avoid committing many-file patches
>right then either.
>
>    
>  
>

Yuck. I think if it gets that far we would have discovered a compelling 
reason to abandon CVS, as many bystanders have urged us to do. But I 
think we can live with an occasional hiccup.


cheers

andrew



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: MultiXactID Wrap-Around
Next
From: Tom Lane
Date:
Subject: Re: MultiXactID Wrap-Around