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

From Tom Lane
Subject Re: Stuck cvs lock on anoncvs repository
Date
Msg-id 24117.1246154999@sss.pgh.pa.us
Whole thread Raw
In response to Re: Stuck cvs lock on anoncvs repository  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Stuck cvs lock on anoncvs repository  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
List pgsql-www
Robert Haas <robertmhaas@gmail.com> writes:
> On Sat, Jun 27, 2009 at 8:09 PM, Marc G. Fournier<scrappy@hub.org> wrote:
>> 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.

This is kind of missing the point, which is that we are talking about
blowing away lockfiles.  Having that happen frequently and automatically
doesn't sound like a particularly good idea.

One thing I'm wondering is why cvs is taking out locks at all, since
it's certainly not committing to the repository.  I guess even a "cvs
update" locks things momentarily, but can we prevent that?
        regards, tom lane


pgsql-www by date:

Previous
From: Robert Haas
Date:
Subject: Re: Stuck cvs lock on anoncvs repository
Next
From: Alvaro Herrera
Date:
Subject: Re: Stuck cvs lock on anoncvs repository