More fail safe incremental update on water_lakeline and water_point (#949)

Improve 97216c5c191bf0df3705134cff234ed980f8ac78 and #853

In case of replay update it may fails because of already existing primary key on osm_id.

Add a on conflict clause to make it fail safe.
This commit is contained in:
Frédéric Rodrigo 2020-07-21 17:35:49 +02:00 committed by GitHub
parent c86f4a557a
commit dd1b2d3b15
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 2 deletions

View File

@ -66,7 +66,10 @@ BEGIN
INSERT INTO osm_water_lakeline INSERT INTO osm_water_lakeline
SELECT * SELECT *
FROM osm_water_lakeline_view FROM osm_water_lakeline_view
WHERE osm_water_lakeline_view.osm_id = NEW.osm_id; WHERE osm_water_lakeline_view.osm_id = NEW.osm_id
-- May happen in case we replay update
ON CONFLICT ON CONSTRAINT osm_water_point_pk
DO NOTHING;
RETURN NULL; RETURN NULL;
END; END;

View File

@ -66,7 +66,10 @@ BEGIN
INSERT INTO osm_water_point INSERT INTO osm_water_point
SELECT * SELECT *
FROM osm_water_point_view FROM osm_water_point_view
WHERE osm_water_point_view.osm_id = NEW.osm_id; WHERE osm_water_point_view.osm_id = NEW.osm_id
-- May happen in case we replay update
ON CONFLICT ON CONSTRAINT osm_water_point_pk
DO NOTHING;
RETURN NULL; RETURN NULL;
END; END;