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:34:50 +0200 (CEST)
Message-ID: <198952269.367235503.1535463290956.JavaMail.root@zimbra82-e14.priv.proxad.net> (raw)
In-Reply-To: <2be8ebca-fecc-51f4-39d7-9869941c679a@posteo.de>
I don't think a vacuum can handle what a pg_dump can't. But I'm maybe wrong.
----- Mail original -----
De: wambacher@posteo.de
À: pgsql-admin@lists.postgresql.org
Envoyé: Mardi 28 Août 2018 15:19:28
Objet: Re: tuple concurrently updated
because it's an OpenStreetMap Full planet database, which is huge (~ 2
TB), i don't have many backups. the last is from 20180608
ok, i can restore that and reload the incremential updates or reload
full data starting from raw data. both will need some days.
if i could get rid of the bad data-record, it's much easier to recover that.
Running a vacuum or a vacuum full, is my last try.
Regards
walter
Am 28.08.2018 um 15:10 schrieb 066ce286@free.fr:
> 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 ?"
>
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: <198952269.367235503.1535463290956.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