From 694bb03d314ff02d43be6ac68e97376e35b720d6 Mon Sep 17 00:00:00 2001 From: bert hubert Date: Sun, 8 Oct 2017 13:41:50 +0200 Subject: [PATCH] add note on how you can't replace the sqlite3 database file while powerdns is running. Also strenghten sqlite3 analyze remark. --- docs/backends/generic-sqlite3.rst | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/backends/generic-sqlite3.rst b/docs/backends/generic-sqlite3.rst index d04e4f327..d3904921d 100644 --- a/docs/backends/generic-sqlite3.rst +++ b/docs/backends/generic-sqlite3.rst @@ -13,7 +13,7 @@ Generic SQLite 3 backend .. warning:: When importing large amounts of data, be sure to run - ``analyze;`` afterwards as SQLite3 has a tendency to use sub-optimal + ``analyze;`` afterwards as SQLite3 has a tendency to use very sub-optimal indexes otherwise. This backend retrieves all data from a SQLite database, which is an @@ -40,6 +40,12 @@ with data. The default setup conforms to the following schema: This schema contains all elements needed for master, slave and superslave operation. +.. warning:: + It is not possible to replace the sqlite3 database file while PowerDNS is + running. Specifically, using ``rsync`` to distribute sqlite3 databases + does not work without stopping PowerDNS first and restarting it after the + change. + After you have created the database you probably want to fill it with data. If you have a BIND zone file it's as easy as: ``zone2sql --named-conf=/path/to/named.conf --gsqlite | sqlite3 powerdns.sqlite3``, -- 2.40.0