Re: tuple concurrently updated - Mailing list pgsql-admin

From wambacher@posteo.de
Subject Re: tuple concurrently updated
Date
Msg-id f737db87-9ca8-a90c-c29d-fd9638a8a3cf@posteo.de
Whole thread Raw
In response to Re: tuple concurrently updated  (wambacher@posteo.de)
Responses Re: tuple concurrently updated  (066ce286@free.fr)
List 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@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.
>


pgsql-admin by date:

Previous
From: Scott Ribe
Date:
Subject: Re: How to get alerted automatically whenever a table structure ischanged between Publisher and Subscriber in Logical Replication?
Next
From: 066ce286@free.fr
Date:
Subject: Re: tuple concurrently updated