From: 066ce286@free.fr
To: wambacher@posteo.de
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: tuple concurrently updated
Date: Tue, 28 Aug 2018 15:10:05 +0200 (CEST)
Message-ID: <114865725.367018989.1535461805284.JavaMail.root@zimbra82-e14.priv.proxad.net> (raw)
In-Reply-To: <f737db87-9ca8-a90c-c29d-fd9638a8a3cf@posteo.de>
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@posteo.de
À: pgsql-admin@lists.postgresql.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@posteo.de:
>
> Am 28.08.2018 um 13:15 schrieb 066ce286@free.fr:
>> Maybe it'll be wise to dump/restore ?
>>
> yes, that may be one option. pg_dump is running right now.
>
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: 066ce286@free.fr, wambacher@posteo.de, pgsql-admin@lists.postgresql.org
Subject: Re: tuple concurrently updated
In-Reply-To: <114865725.367018989.1535461805284.JavaMail.root@zimbra82-e14.priv.proxad.net>
* 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