Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fudl6-0007qo-4U for pgsql-admin@arkaria.postgresql.org; Tue, 28 Aug 2018 13:10:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fudl4-0005au-Jl for pgsql-admin@arkaria.postgresql.org; Tue, 28 Aug 2018 13:10:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from <066ce286@free.fr>) id 1fudl4-0005ag-C9 for pgsql-admin@lists.postgresql.org; Tue, 28 Aug 2018 13:10:10 +0000 Received: from smtp1-g21.free.fr ([212.27.42.1]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from <066ce286@free.fr>) id 1fudl1-0002NW-B2 for pgsql-admin@lists.postgresql.org; Tue, 28 Aug 2018 13:10:09 +0000 Received: from zimbra82-e14.priv.proxad.net (unknown [172.20.243.235]) by smtp1-g21.free.fr (Postfix) with ESMTP id 690A9B00585; Tue, 28 Aug 2018 15:10:05 +0200 (CEST) Date: Tue, 28 Aug 2018 15:10:05 +0200 (CEST) From: 066ce286@free.fr To: wambacher@posteo.de Cc: pgsql-admin@lists.postgresql.org Message-ID: <114865725.367018989.1535461805284.JavaMail.root@zimbra82-e14.priv.proxad.net> In-Reply-To: Subject: Re: tuple concurrently updated MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [2a01:e35:2434:2250:8c8e:8d27:9c28:8ea3] X-Mailer: Zimbra 7.2.0-GA2598 (ZimbraWebClient - GC68 (Linux)/7.2.0-GA2598) X-Authenticated-User: 066ce286@free.fr List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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/arch= ivelogs ?" ----- Mail original ----- De: wambacher@posteo.de =C3=80: pgsql-admin@lists.postgresql.org Envoy=C3=A9: Mardi 28 Ao=C3=BBt 2018 15:04:14 Objet: Re: tuple concurrently updated pg_dump not completed: pg_dump: Ausgabe des Inhalts der Tabelle =C2=BBplanet_osm_line=C2=AB fehlgeschlagen: PQgetResult() fehlgeschlagen. pg_dump: Fehlermeldung vom Server: FEHLER:=C2=A0 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. >