| From: | Flavio Henrique Araque Gurgel <fhagur(at)gmail(dot)com> |
|---|---|
| To: | wambacher(at)posteo(dot)de |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: tuple concurrently updated |
| Date: | 2018-08-28 11:20:26 |
| Message-ID: | CAGHTAeMDRiB0wRXby6M3PCsv+9QLbBNxoDENTm=cCg3b1-DsxQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Em ter, 28 de ago de 2018 às 13:18, Flavio Henrique Araque Gurgel <
fhagur(at)gmail(dot)com> escreveu:
> Em ter, 28 de ago de 2018 às 13:15, <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.
>
>
My mistake, it's pg_prepared_xacts the correct name.
Flavio Gurgel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | wambacher | 2018-08-28 11:23:25 | Re: tuple concurrently updated |
| Previous Message | Flavio Henrique Araque Gurgel | 2018-08-28 11:18:06 | Re: tuple concurrently updated |