From: wambacher@posteo.de
To: pgsql-admin@lists.postgresql.org
Subject: Re: tuple concurrently updated
Date: Tue, 28 Aug 2018 13:23:25 +0200
Message-ID: <f8cfb91f-a205-0530-25df-09f806d7ca5c@posteo.de> (raw)
In-Reply-To: <CAGHTAeMDw7Qd6zkwkxYb36BHGaoCPXk6Q-a8MCNkyT8FOrkbKg@mail.gmail.com>
References: <1378566276.366027624.1535454005687.JavaMail.root@zimbra82-e14.priv.proxad.net>
<12cf1bbf-be58-bd2e-af34-85e72592a866@posteo.de>
<CAGHTAeMDw7Qd6zkwkxYb36BHGaoCPXk6Q-a8MCNkyT8FOrkbKg@mail.gmail.com>
pg_prepared_transactions does not exist, or i don't know how to list that
Am 28.08.2018 um 13:18 schrieb Flavio Henrique Araque Gurgel:
>
>
> Em ter, 28 de ago de 2018 às 13:15, <wambacher@posteo.de
> <mailto:wambacher@posteo.de>> escreveu:
>
> 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.
>
> Look if you have prepared transactions on the pg_prepared_transactions
> view.
> If you make use of JDBC it's possible that you use it without knowing
> and it survives Postgres restarts.
> If you have any, drop them.
>
> Flavio Gurgel
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: wambacher@posteo.de, pgsql-admin@lists.postgresql.org
Subject: Re: tuple concurrently updated
In-Reply-To: <f8cfb91f-a205-0530-25df-09f806d7ca5c@posteo.de>
* 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