From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 876481F8DF for ; Wed, 1 Jul 2020 21:06:20 +0000 (UTC) From: Eric Wong To: meta@public-inbox.org Subject: [PATCH 5/5] overidx: document why we don't use SQLite WAL Date: Wed, 1 Jul 2020 21:06:19 +0000 Message-Id: <20200701210619.29601-6-e@yhbt.net> In-Reply-To: <20200701210619.29601-1-e@yhbt.net> References: <20200701210619.29601-1-e@yhbt.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: I was wondering about this myself the other day and had to read up on it. So make a note of it for future readers. --- lib/PublicInbox/OverIdx.pm | 2 ++ 1 file changed, 2 insertions(+) diff --git a/lib/PublicInbox/OverIdx.pm b/lib/PublicInbox/OverIdx.pm index c7f45a6c910..008a5d1a936 100644 --- a/lib/PublicInbox/OverIdx.pm +++ b/lib/PublicInbox/OverIdx.pm @@ -23,6 +23,8 @@ sub dbh_new { my $dbh = $self->SUPER::dbh_new(1); # TRUNCATE reduces I/O compared to the default (DELETE) + # We do not use WAL since we're optimized for read-only ops, + # (and read-only requires SQLite 3.22.0 (2018-01-22)). $dbh->do('PRAGMA journal_mode = TRUNCATE'); # 80000 pages (80MiB on SQLite <3.12.0, 320MiB on 3.12.0+)