From: | wambacher(at)posteo(dot)de |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: tuple concurrently updated |
Date: | 2018-08-28 16:54:46 |
Message-ID: | 1d365869-b2eb-49c6-ba9d-968d7fc49d69@posteo.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
got it - vacuum analyze on that table solved the problem. think, there
was one index corrupt and not the data.
thanks to all
walter
Am 28.08.2018 um 12:36 schrieb wambacher(at)posteo(dot)de:
> Hi,
>
> getting this error:
>
> DELETE FROM planet_osm_line WHERE osm_id = -166570;
> FEHLER: tuple concurrently updated
>
> postgresql 10.1
>
> any idea what i can do? of course i did a restart first.
>
> regards
>
> walter
>
>
--
My projects:
Admin Boundaries of the World <https://wambachers-osm.website/boundaries>
Missing Boundaries
<https://wambachers-osm.website/index.php/projekte/internationale-administrative-grenzen/missing-boundaries>
Emergency Map <https://wambachers-osm.website/emergency>
Postal Code Map (Germany only) <https://wambachers-osm.website/plz>
Fools (QA for zipcodes in Germany) <https://wambachers-osm.website/fools>
Postcode Boundaries of Germany <https://wambachers-osm.website/pcoundaries>
From | Date | Subject | |
---|---|---|---|
Next Message | Evan Bauer | 2018-08-28 16:57:59 | Re: More efficient pg_restore method? |
Previous Message | Ron | 2018-08-28 16:48:48 | More efficient pg_restore method? |