From: | wambacher(at)posteo(dot)de |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: got error: DELETE FROM planet_osm_line WHERE osm_id = -390840 failed: FEHLER: tuple concurrently updated |
Date: | 2019-10-11 20:56:37 |
Message-ID: | 88cb51a4-3c8d-d62d-e4e3-106f7da1de47@posteo.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Adrin,
Am 11.10.19 um 21:42 schrieb Adrian Klaver:
> On 10/11/19 10:28 AM, wambacher(at)posteo(dot)de wrote:
>> Hi, after a crash i get this errpor: DELETE FROM planet_osm_line
>> WHERE osm_id = -390840 failed: FEHLER: tuple concurrently updated
>>
>> any idea what i can do?
>
> More information would be helpful:
>
> 1) Postgres version?
10.1
>
> 2) What is logged just before the crash?
will have to check this later.
>
> 3) By crash do you mean the Postgres server shuts down?
no, system hang and i had to do a power reset (nothing else helped)
>
> 4) Does this happen every time you delete -390840?
yes
>
> 5) Is -390840 really the value?
yes
> If so what is the definition for the osm_id column?
bigint,
index "planet_osm_line_pkey" btree (osm_id), Tablespace »planet3_is1
and there is no trigger on this table.
i wrote a pg/plsql function reading the table line by line using an
exception condition and writing all records to a new table. program is
running and some records have been ignored. it is quite easy to re-add
the missing records - hope so.
regards
walter
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-10-11 22:06:08 | Re: got error: DELETE FROM planet_osm_line WHERE osm_id = -390840 failed: FEHLER: tuple concurrently updated |
Previous Message | Adrian Klaver | 2019-10-11 19:47:36 | Re: got error: DELETE FROM planet_osm_line WHERE osm_id = -390840 failed: FEHLER: tuple concurrently updated |