From 3c9e09545e4a3955e0454097df9e5adcaa212d3d Mon Sep 17 00:00:00 2001 From: Sarah Hoffmann Date: Sat, 6 Mar 2021 16:38:37 +0100 Subject: [PATCH] documentation for new migration command --- docs/admin/Migration.md | 25 ++++++++++++------------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/docs/admin/Migration.md b/docs/admin/Migration.md index dc94310b..52970a33 100644 --- a/docs/admin/Migration.md +++ b/docs/admin/Migration.md @@ -1,22 +1,21 @@ # Database Migrations -This page describes database migrations necessary to update existing databases -to newer versions of Nominatim. +Since version 3.7.0 Nominatim offers automatic migrations. Please follow +the following steps: -SQL statements should be executed from the PostgreSQL commandline. Execute -`psql nominatim` to enter command line mode. +* stop any updates that are potentially running +* update Nominatim to the nwer version +* goto your project directory and run `nominatim admin --migrate` +* (optionally) restart updates -## 3.6.0 -> master - -### Status table contains now time zone information +Below you find additional migrations and hints about other structural and +breaking changes. -The `import_status` table has been changed to include timezone information -with the time stamp. You need to alter an existing table before running -any replication functions with: +!!! note + If you are migrating from a version <3.6, then you still have to follow + the manual migration steps up to 3.6. -```sql -ALTER TABLE import_status ALTER COLUMN lastimportdate TYPE timestamp with time zone; -``` +## 3.6.0 -> master ### New location for data files -- 2.39.5