Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Stuck cvs lock on anoncvs repository

  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
  • Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "Marc G. Fournier" <scrappy(at)hub(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, pgsql-www(at)postgresql(dot)org
  • Subject: Re: Stuck cvs lock on anoncvs repository
  • Date: Sun, 28 Jun 2009 10:17:50 -0400
  • Message-id: <7040.1246198670@sss.pgh.pa.us> <text/plain>
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
Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group