Re: tuple concurrently updated

From: wambacher(at)posteo(dot)de
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: tuple concurrently updated
Date: 2018-08-28 13:04:14
Message-ID: f737db87-9ca8-a90c-c29d-fd9638a8a3cf@posteo.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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.
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message 066ce286 2018-08-28 13:10:05 Re: tuple concurrently updated
Previous Message Scott Ribe 2018-08-28 12:11:52 Re: How to get alerted automatically whenever a table structure is changed between Publisher and Subscriber in Logical Replication?