From: 066ce286@free.fr
To: wambacher@posteo.de
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: tuple concurrently updated
Date: Tue, 28 Aug 2018 13:15:38 +0200 (CEST)
Message-ID: <1233975696.366149748.1535454938944.JavaMail.root@zimbra82-e14.priv.proxad.net> (raw)
In-Reply-To: <99342cd8-c2f6-31bd-f8e4-5c65658b1a2f@posteo.de>
Maybe it'll be wise to dump/restore ?
----- Mail original -----
De: wambacher@posteo.de
À: 066ce286@free.fr
Cc: pgsql-admin@lists.postgresql.org
Envoyé: Mardi 28 Août 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 planet_osm_line I presume.
>
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: <1233975696.366149748.1535454938944.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