Re: tuple concurrently updated

BTW you have data corruption.

So forget your problem about concurrent updates ; that's not the clue.

Your new question should be how to recover corrupted table.

Sorry, I've no skill for that problem other that "how ran your backups/archivelogs ?"

----- Mail original -----
De: wambacher(at)posteo(dot)de
À: pgsql-admin(at)lists(dot)postgresql(dot)org
Envoyé: Mardi 28 Août 2018 15:04:14
Objet: Re: tuple concurrently updated

pg_dump not completed:

pg_dump: Ausgabe des Inhalts der Tabelle »planet_osm_line«
fehlgeschlagen: PQgetResult() fehlgeschlagen.
pg_dump: Fehlermeldung vom Server: FEHLER:  unexpected chunk number 0
(expected 1) for toast value 1261719035 in pg_toast_1340113

anything else i can do?

regards
walter
Am 28.08.2018 um 13:25 schrieb wambacher(at)posteo(dot)de:
>
> Am 28.08.2018 um 13:15 schrieb 066ce286(at)free(dot)fr:
>> Maybe it'll be wise to dump/restore ?
>>
> yes, that may be one option. pg_dump is running right now.
>