Hi Walter,
Why can't you go with a postgres service restart in order to get rid of this
error?
>DELETE FROM planet_osm_line WHERE osm_id = -166570;
>FEHLER: tuple concurrently updated
Concurrent transactions can update or delete one or more of those rows
before DELETE can lock the rows (at least with the default isolation level
READ COMMITTED). This would result in your error message.
To defend against this race condition, lock the rows in the SELECT with FOR
UPDATE (or other options)
Regards,
Pavan
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
