Postgres Pro
Downloads
Home   >   mailing lists

Re: deadlock in single-row select-for-update + update scenario? How could it happen? - Mailing list pgsql-general

From Adrian Klaver
Subject Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Date
Msg-id 53F783D1.7030602@aklaver.com
Whole thread Raw
In response to Re: deadlock in single-row select-for-update + update scenario? How could it happen?  (hubert depesz lubaczewski <depesz@gmail.com>)
Responses Re: deadlock in single-row select-for-update + update scenario? How could it happen?  (hubert depesz lubaczewski <depesz@gmail.com>)
List pgsql-general
Tree view 
On 08/22/2014 10:50 AM, hubert depesz lubaczewski wrote:
> On Fri, Aug 22, 2014 at 7:43 PM, Adrian Klaver
> <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
>
>     Which begs the question, what is different about that machine?
>
>
> No idea. I can pass all the question you might have, but I'm ~ 6000
> miles away from any machine running this code.

Which in itself might be a clue.

Is all the code/data running on/coming from that machine or is some
coming in remotely?

Where network latency might be an issue?

>
> depesz


--
Adrian Klaver
adrian.klaver@aklaver.com

pgsql-general by date:

Previous
From: hubert depesz lubaczewski
Date:
Subject: Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Next
From: hubert depesz lubaczewski
Date:
Subject: Re: deadlock in single-row select-for-update + update scenario? How could it happen?