From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: wambacher@posteo.de
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: tuple concurrently updated
Date: Tue, 28 Aug 2018 10:51:34 -0300
Message-ID: <20180828135134.o4ymb6vvitpfcmxc@alvherre.pgsql> (raw)
In-Reply-To: <986488f7-ff29-5dff-9425-5fcd6dcbb68a@posteo.de>
On 2018-Aug-28, wambacher@posteo.de wrote:
> 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.
What is the definition of the table? It sounds like there's some GIS
datatype -- Right? Are there any triggers or some other fun fact about
this delete? What is the isolation level in effect when the delete
runs?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: alvherre@2ndquadrant.com, wambacher@posteo.de, pgsql-admin@lists.postgresql.org
Subject: Re: tuple concurrently updated
In-Reply-To: <20180828135134.o4ymb6vvitpfcmxc@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox