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 1fubyM-0001v0-Vh for pgsql-admin@arkaria.postgresql.org; Tue, 28 Aug 2018 11:15:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fubyL-0000Yt-9o for pgsql-admin@arkaria.postgresql.org; Tue, 28 Aug 2018 11:15:45 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from <066ce286@free.fr>) id 1fubyK-0000Ym-VA for pgsql-admin@lists.postgresql.org; Tue, 28 Aug 2018 11:15:45 +0000 Received: from smtp5-g21.free.fr ([2a01:e0c:1:1599::14]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from <066ce286@free.fr>) id 1fubyI-0003UK-C5 for pgsql-admin@lists.postgresql.org; Tue, 28 Aug 2018 11:15:43 +0000 Received: from zimbra82-e14.priv.proxad.net (unknown [172.20.243.235]) by smtp5-g21.free.fr (Postfix) with ESMTP id 1301E5FFBA; Tue, 28 Aug 2018 13:15:39 +0200 (CEST) Date: Tue, 28 Aug 2018 13:15:38 +0200 (CEST) From: 066ce286@free.fr To: wambacher@posteo.de Cc: pgsql-admin@lists.postgresql.org Message-ID: <1233975696.366149748.1535454938944.JavaMail.root@zimbra82-e14.priv.proxad.net> In-Reply-To: <99342cd8-c2f6-31bd-f8e4-5c65658b1a2f@posteo.de> 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 Maybe it'll be wise to dump/restore ? ----- Mail original ----- De: wambacher@posteo.de =C3=80: 066ce286@free.fr Cc: pgsql-admin@lists.postgresql.org Envoy=C3=A9: Mardi 28 Ao=C3=BBt 2018 13:08:59 Objet: Re: tuple concurrently updated Hi, there is only one process updating my database. and that is exactly the job which is getting the error. all other jobs are read/only and i even stoppend those. but there has been a crash some hours ago and the db "recovered". Am 28.08.2018 um 13:00 schrieb 066ce286@free.fr: > You may have others transactions opened modifying this line of table plan= et_osm_line I presume. >