From: Sarah Hoffmann <lonvia@denofr.de>
Date: Mon, 24 Feb 2020 21:42:03 +0000 (+0100)
Subject: revert using stricter uniqueness constraint on place
X-Git-Tag: v3.5.0~73
X-Git-Url: https://git.openstreetmap.org./nominatim.git/commitdiff_plain/0e3252f045739cdc5cf845bf9467ea47dfd9bd9a

revert using stricter uniqueness constraint on place

Multiple objects with the same (osm_type, osm_id, class) may
exist when we hold back deleting an area because it is so
large.

Fixes #1695.
---

diff --git a/sql/indices_updates.src.sql b/sql/indices_updates.src.sql
index 99f59cdb..175bfba2 100644
--- a/sql/indices_updates.src.sql
+++ b/sql/indices_updates.src.sql
@@ -6,4 +6,4 @@ CREATE INDEX CONCURRENTLY idx_placex_pendingsector ON placex USING BTREE (rank_s
 CREATE INDEX CONCURRENTLY idx_location_area_country_place_id ON location_area_country USING BTREE (place_id) {ts:address-index};
 
 DROP INDEX CONCURRENTLY IF EXISTS place_id_idx;
-CREATE UNIQUE INDEX CONCURRENTLY idx_place_osm_unique on place using btree(osm_id,osm_type,class) {ts:address-index};
+CREATE UNIQUE INDEX CONCURRENTLY idx_place_osm_unique on place using btree(osm_id,osm_type,class,type) {ts:address-index};