From: | wambacher(at)posteo(dot)de |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: tuple concurrently updated |
Date: | 2018-08-28 11:23:25 |
Message-ID: | f8cfb91f-a205-0530-25df-09f806d7ca5c@posteo.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(at)posteo(dot)de
> <mailto:wambacher(at)posteo(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | wambacher | 2018-08-28 11:25:48 | Re: tuple concurrently updated |
Previous Message | Flavio Henrique Araque Gurgel | 2018-08-28 11:20:26 | Re: tuple concurrently updated |