From de23e2a2767a7448d3a79e13a5ff4665ef41587e Mon Sep 17 00:00:00 2001 From: 010011110 Date: Mon, 26 Oct 2026 06:59:43 +0100 Subject: [PATCH] Note that FTL v7.0 has no in-memory or temporary query database Signed-off-by: 010011110 --- docs/database/query-database.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/database/query-database.md b/docs/database/query-database.md index 463f5d3de..51964ddd5 100644 --- a/docs/database/query-database.md +++ b/docs/database/query-database.md @@ -9,6 +9,8 @@ Another way of controlling the size of the long-term database is by setting a ma The config parameter `database.DBimport` controls whether `FTL` loads information from the database on startup. It needs to do this to populate the internal data structure with the most recent history. However, as importing from the database on disk can delay FTL on very large deploys, it can be disabled using this option. +Since FTL v7.0, the recent query history lives in shared memory only, and FTL writes new queries from there straight into the database every `database.DBinterval` and when it stops. The in-memory and temporary query databases of earlier versions are gone, and with them the options `database.forceDisk` and `files.tmp_db`. A `/etc/pihole/pihole-tmp.db` left behind by an earlier version is no longer used and can be deleted, and Docker setups can drop the environment variables `FTLCONF_database_forceDisk` and `FTLCONF_files_tmp_db`. + --- ### Split database