From c5d06cf382ff07880220d57e12e1c2e5b843e701 Mon Sep 17 00:00:00 2001 From: Ingo Schwarze Date: Sat, 18 Jan 2014 08:19:18 +0000 Subject: Despite some experimenting, i'm unable to find any relevant effect of creating an index for the keys table on apropos(1) search times; apparently, adding that index was premature optimization in the first place; so, stop adding that index. Its root gone, the following evil is reduced (/usr/share/man on my notebook) - DB build time with -Q goes down by 15%, now at 1/3 of makewhatis - DB size with -Q goes down by 35%, now at 3.5x of makewhatis - full DB build time goes down by 12%, now at 2.1x of makewhatis - full DB size goes down by 42%, now at 11.5x of makewhatis --- mandocdb.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'mandocdb.c') diff --git a/mandocdb.c b/mandocdb.c index f3ac5481..cd02b2b5 100644 --- a/mandocdb.c +++ b/mandocdb.c @@ -1924,9 +1924,7 @@ dbopen(int real) " \"pageid\" INTEGER NOT NULL REFERENCES mpages(id) " "ON DELETE CASCADE,\n" " \"id\" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL\n" - ");\n" - "\n" - "CREATE INDEX \"key_index\" ON keys (key);\n"; + ");\n"; if (SQLITE_OK != sqlite3_exec(db, sql, NULL, NULL, NULL)) { exitcode = (int)MANDOCLEVEL_SYSERR; -- cgit