Re: Stuck cvs lock on anoncvs repository - Mailing list pgsql-www

From Robert Haas
Subject Re: Stuck cvs lock on anoncvs repository
Date
Msg-id 603c8f070906271906g1a70dcdci64c7306c46bd289@mail.gmail.com
Whole thread Raw
In response to Re: Stuck cvs lock on anoncvs repository  ("Marc G. Fournier" <scrappy@hub.org>)
Responses Re: Stuck cvs lock on anoncvs repository  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Stuck cvs lock on anoncvs repository  (Magnus Hagander <magnus@hagander.net>)
List pgsql-www
On Sat, Jun 27, 2009 at 8:09 PM, Marc G. Fournier<scrappy@hub.org> wrote:
> On Sat, 27 Jun 2009, Alvaro Herrera wrote:
>
>> Stefan Kaltenbrunner escribió:
>>>
>>> Greg Stark wrote:
>>>>
>>>> do we not have --delete on the rsync command? why doesn't the problem
>>>> go away on the next sync if we do?
>>>
>>> we do use --delete - but nobody commited after we tagged and before the
>>> problem got reported so the regular on-commit code didn't kick in and
>>> forced syncs only happen once a day.
>>
>> Are we worried about bandwidth wastage that we don't run it more often?
>
> More often then when ppl commit?  What would be the point to that?

Well, the whole point of using rsync is that it only copies what has
changed, so there is very little overhead involved in running it when
nothing has changed.  If our current system is adding an additional
layer of "did anything change?" checking, it's unnecessarily
duplicating functionality which is already implemented really, really
well by rsync.

If updating the exclude list is sufficient to fix the problem, maybe
it's not worth worrying about.  But on the other hand maybe we should
just rsync it every 15 minutes and forget about it.

...Robert


pgsql-www by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] pull raw text of a message by message-id
Next
From: Tom Lane
Date:
Subject: Re: Stuck cvs lock on anoncvs repository