user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: anybody hit SQLite "database is locked" errors?
Date: Tue, 25 Aug 2020 00:12:04 +0000	[thread overview]
Message-ID: <20200825001204.GA840@dcvr> (raw)

Hey all, I've been reindexing frequently ahead of THREADED changes
while another process is doing grok-pull and triggering SQLite
reads in the post_update_hook.

This problem causes an exception in the --reindex process
because a read-only SQLite process is holding a SHARED lock.

In particular, the expensive (for LKML) `SELECT COUNT(*) FROM msgmap'
statement in our current examples/
seems to be a culprit.  That's even opened with the sqlite3
`-readonly' flag, it still needs to acquire a SHARED lock in SQLite.

Other statements run by -httpd/-nntpd/-imapd may still cause
this, I think; but I haven't seen it...  Maybe others have?

WAL (write-ahead-log in SQLite) would be nice; but we can't use
it since we expect writers (-mda/-watch) to be a different Unix
user than -httpd/-nntpd/-imapd.

The Perl binding we use, DBD::SQLite sets it to 30000ms by
default, but the busy handler doesn't get fired in these cases.
See comments for sqlite3PagerSetBusyHandler in src/pager.c:

(SQLite itself doesn't enable by busy handler by default, DBD::SQLite does)

I'm thinking of some possible solutions around it, but they're
fairly ugly and would make reads more expensive...  SQLite
itself seems saddled with retaining Windows 95 compatibility;
something we obviously won't have to care about.

             reply	other threads:[~2020-08-25  0:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25  0:12 Eric Wong [this message]
2020-08-25 10:23 ` [PATCH] grok-pull.post_update_hook: flock(2) before SQLite check Eric Wong
2020-08-25 16:29 ` anybody hit SQLite "database is locked" errors? Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200825001204.GA840@dcvr \ \ \
    --subject='Re: anybody hit SQLite "database is locked" errors?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).