| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "'Thomas Kellerer *EXTERN*'" <spam_eater(at)gmx(dot)net>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Confusing deadlock report |
| Date: | 2016-03-16 15:09:57 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B53810A39@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thomas Kellerer wrote:
>> Can you determine what statements were executed in these transactions before the deadlock?
>> It was probably one of these that took the conflicting lock.
>
> Unfortunately not. Statement logging is not enabled on that server (space-constrained).
>
> And while we know the statements that can possibly be executed by these parts of the application,
> several on them depend on the actual data, so it's hard to tell which path the two transactions
> actually used.
But that's where the solution to your problem must be...
Look at all statements that modify "alpha" and could be in the same transaction
with the INSERT to "bravo".
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2016-03-16 15:19:00 | Re: log temp files are created twice in PL/pgSQL function |
| Previous Message | Dang Minh Huong | 2016-03-16 14:58:48 | log temp files are created twice in PL/pgSQL function |