mirror of
https://github.com/osm-search/Nominatim.git
synced 2026-02-15 19:07:58 +00:00
e7b738fe35
Remove level 3 (page title) from TOC and add permalinks. Also fix and update some minor stuff in the docs.
77 lines
2.3 KiB
Markdown
77 lines
2.3 KiB
Markdown
# Database Migrations
|
|
|
|
This page describes database migrations necessary to update existing databases
|
|
to newer versions of Nominatim.
|
|
|
|
SQL statements should be executed from the postgres commandline. Execute
|
|
`psql nominiatim` to enter command line mode.
|
|
|
|
## 3.0.0 -> 3.1.0
|
|
|
|
### Postcode Table
|
|
|
|
A new separate table for artificially computed postcode centroids was introduced.
|
|
Migration to the new format is possible but **not recommended**.
|
|
|
|
Create postcode table and indexes, running the following SQL statements:
|
|
|
|
```sql
|
|
CREATE TABLE location_postcode
|
|
(place_id BIGINT, parent_place_id BIGINT, rank_search SMALLINT,
|
|
rank_address SMALLINT, indexed_status SMALLINT, indexed_date TIMESTAMP,
|
|
country_code varchar(2), postcode TEXT,
|
|
geometry GEOMETRY(Geometry, 4326));
|
|
CREATE INDEX idx_postcode_geometry ON location_postcode USING GIST (geometry);
|
|
CREATE UNIQUE INDEX idx_postcode_id ON location_postcode USING BTREE (place_id);
|
|
CREATE INDEX idx_postcode_postcode ON location_postcode USING BTREE (postcode);
|
|
GRANT SELECT ON location_postcode TO "www-data";
|
|
drop type if exists nearfeaturecentr cascade;
|
|
create type nearfeaturecentr as (
|
|
place_id BIGINT,
|
|
keywords int[],
|
|
rank_address smallint,
|
|
rank_search smallint,
|
|
distance float,
|
|
isguess boolean,
|
|
postcode TEXT,
|
|
centroid GEOMETRY
|
|
);
|
|
```
|
|
|
|
Add postcode column to `location_area` tables with SQL statement:
|
|
|
|
```sql
|
|
ALTER TABLE location_area ADD COLUMN postcode TEXT;
|
|
```
|
|
|
|
Then reimport the functions:
|
|
|
|
```sh
|
|
./utils/setup.php --create-functions --enable-diff-updates --create-partition-functions
|
|
```
|
|
|
|
Create appropriate triggers with SQL:
|
|
|
|
```sql
|
|
CREATE TRIGGER location_postcode_before_update BEFORE UPDATE ON location_postcode
|
|
FOR EACH ROW EXECUTE PROCEDURE postcode_update();
|
|
```
|
|
|
|
Finally populate the postcode table (will take a while):
|
|
|
|
```sh
|
|
./utils/setup.php --calculate-postcodes --index --index-noanalyse
|
|
```
|
|
|
|
This will create a working database. You may also delete the old artificial
|
|
postcodes now. Note that this may be expensive and is not absolutely necessary.
|
|
The following SQL statement will remove them:
|
|
|
|
```sql
|
|
DELETE FROM place_addressline a USING placex p
|
|
WHERE a.address_place_id = p.place_id and p.osm_type = 'P';
|
|
ALTER TABLE placex DISABLE TRIGGER USER;
|
|
DELETE FROM placex WHERE osm_type = 'P';
|
|
ALTER TABLE placex ENABLE TRIGGER USER;
|
|
```
|