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: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
  • To: "Marc G. Fournier" <scrappy(at)hub(dot)org>
  • Cc: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Greg Stark <gsstark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 00:08:53 -0400
  • Message-id: <20090628040853.GB23557@alvh.no-ip.org> <text/plain>

Marc G. Fournier escribió:
> 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?

Avoiding the precise problem that this thread is about, of course.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support



Home | Main Index | Thread Index

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