X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=Jce8o9vhLjUGT1RltNPdAHOwU2ebr+2Ltvnm9uPUkM8HVQoACvi/Z
	WY2uLAo4xvTH6YxljVrjYKPTcak8rmAhUp7f4jOHroNdgtdCtEiuMxkmgH0AKWKa
	p6WspJfFxgQblyRQ5e14NrsP/O68urUL8A1Dm9Lw4PrFeHsQ2FYe1Y=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=eLSizdNsfF4v3y29TP98Uh7XQRI=; b=WstTMPXKa8QVka3kC5y4fBVtTMNd
	cHXgg7FPesVAzSy1bc2Ao+gtLJEpZDL4jGKXGqtzQTlJ7K2RAKnBAL55sGOtENt1
	+3z/1T9VCB3Pyl9ZDLtbWFFqKvRj5NwzDC+My8irIFZP6OT3bZPCnwBidpn5NVr+
	56P1Joqzq022U4U=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status:	No, score=-1.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1
Date:	Sat, 1 Jun 2013 12:58:13 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: sqlite3: bug with monotone
Message-ID:	<20130601105813.GD30659@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<51A6B6EB DOT 6050309 AT users DOT sourceforge DOT net> <loom DOT 20130530T122354-144 AT post DOT gmane DOT org> <51A7862F DOT 1070507 AT etr-usa DOT com> <51A7D47E DOT 3050502 AT users DOT sourceforge DOT net> <51A7F547 DOT 6020509 AT etr-usa DOT com> <20130531092228 DOT GB30659 AT calimero DOT vinschen DOT de> <51A900EF DOT 2020606 AT etr-usa DOT com> <51A905DC DOT 6020109 AT etr-usa DOT com>
MIME-Version:	1.0
In-Reply-To:	<51A905DC.6020109@etr-usa.com>
User-Agent:	Mutt/1.5.21 (2010-09-15)

On May 31 14:19, Warren Young wrote:
> On 5/31/2013 13:58, Warren Young wrote:
> >
> >The SQLite code prefers POSIX advisory locks, but it can fall back to
> >BSD locks if it has to.
> 
> Just to clarify, when I say "POSIX locks" I always mean new style
> fcntl() locks.  There are no calls to lockf() in sqlite3.c.
> 
> >I'm not sure why it doesn't just
> >blindly try the lock.
> 
> On reflection, I'm sure it has something to do with maintaining high
> concurrency.  If it knows its near-future DB file write is going to
> get blocked, it can choose to do something else while the existing
> DB lock holders finish.
> 
> By contrast, SQLite's flock() based locking is documented as being
> much more brute-force, resulting in much lower concurrency.

Makes sense, given that flock is not record but file locking.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -