From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 865391F66E;
	Tue, 25 Aug 2020 16:29:05 +0000 (UTC)
Date: Tue, 25 Aug 2020 16:29:05 +0000
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: anybody hit SQLite "database is locked" errors?
Message-ID: <20200825162905.GA4005@dcvr>
References: <20200825001204.GA840@dcvr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20200825001204.GA840@dcvr>
List-Id: <meta.public-inbox.org>

Eric Wong <e@80x24.org> wrote:
> In particular, the expensive (for LKML) `SELECT COUNT(*) FROM msgmap'
> statement in our current examples/grok-pull.post_update_hook.sh
> seems to be a culprit.  That's even opened with the sqlite3
> `-readonly' flag, it still needs to acquire a SHARED lock in SQLite.

Even without the proposed patch to the post_update_hook;
I haven't been able to reproduce the problem on a different
(faster) machine...