From 5884a6e7a674a5f32a41ff6d392416eac6d230fd Mon Sep 17 00:00:00 2001 From: Sarah Hoffmann Date: Fri, 19 Nov 2021 16:11:32 +0100 Subject: [PATCH] add a section about moving the database to another machine --- docs/admin/Advanced-Installations.md | 48 +++++++++++++++++++++++++++- 1 file changed, 47 insertions(+), 1 deletion(-) diff --git a/docs/admin/Advanced-Installations.md b/docs/admin/Advanced-Installations.md index 98a3b64a..ff267cee 100644 --- a/docs/admin/Advanced-Installations.md +++ b/docs/admin/Advanced-Installations.md @@ -101,7 +101,7 @@ This will get diffs from the replication server, import diffs and index the database. The default replication server in the script([Geofabrik](https://download.geofabrik.de)) provides daily updates. -## Importing Nominatim to an external PostgreSQL database +## Using an external PostgreSQL database You can install Nominatim using a database that runs on a different server when you have physical access to the file system on the other server. Nominatim @@ -109,6 +109,11 @@ uses a custom normalization library that needs to be made accessible to the PostgreSQL server. This section explains how to set up the normalization library. +!!! note + The external module is only needed when using the legacy tokenizer. + If you have choosen the ICU tokenizer, then you can ignore this section + and follow the standard import documentation. + ### Option 1: Compiling the library on the database server The most sure way to get a working library is to compile it on the database @@ -167,3 +172,44 @@ NOMINATIM_DATABASE_MODULE_PATH="