Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> Tom Lane wrote:
>> 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?
> the problem is that we transferred the locks from cvs.postgresql.org to
> anoncvs.postgresql.org which confused cvs running on anoncvs.
Ah, now I understand. Yes, sounds like a simple --exclude will fix it.
regards, tom lane
In response to
pgsql-www by date
|Next:||From: webmaster||Date: 2009-06-29 14:00:00|
|Subject: PostgreSQL moderation report: 2009-6-29|
|Previous:||From: Robert Haas||Date: 2009-06-28 12:06:02|
|Subject: Re: Stuck cvs lock on anoncvs repository|