hans/Nominatim
1
0
Fork 1
mirror of https://github.com/osm-search/Nominatim.git synced 2026-02-15 19:07:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

consolidate indexes over geometry_sectors

Browse Source 
The index over geometry_sectors are mainly used for ordering
the places which need indexing. That means they function effectively
as a TODO list. Consolodate them so that they always only contain
the places which are still to do. Also add the appropriate index
for the boundary indexing phase.
This commit is contained in:
Sarah Hoffmann
2022-09-21 10:38:58 +02:00
parent 860f3559a1
commit f4d3ae6f70
5 changed files with 25 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
lib-sql/indices.sql
View File

@@ -5,6 +5,13 @@
-- Copyright (C) 2022 by the Nominatim developer community.
-- For a full list of authors see the git log.
-- The following indicies are only useful during imoprt when all of placex is processed.
{% if drop %}
DROP INDEX IF EXISTS idx_placex_rank_address_sector;
DROP INDEX IF EXISTS idx_placex_rank_boundaries_sector;
{% endif %}
-- Indices used only during search and update.
-- These indices are created only after the indexing process is done.
@@ -39,10 +46,6 @@ CREATE INDEX IF NOT EXISTS idx_postcode_postcode
-- Indices only needed for updating.
{% if not drop %}
---
CREATE INDEX IF NOT EXISTS idx_placex_pendingsector
ON placex USING BTREE (rank_address,geometry_sector) {{db.tablespace.address_index}}
WHERE indexed_status > 0;
---
CREATE INDEX IF NOT EXISTS idx_location_area_country_place_id
ON location_area_country USING BTREE (place_id) {{db.tablespace.address_index}};