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

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: hubert depesz lubaczewski <depesz(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Date: 2014-08-22 17:54:25
Message-ID: 53F783D1.7030602@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 08/22/2014 10:50 AM, hubert depesz lubaczewski wrote:
> On Fri, Aug 22, 2014 at 7:43 PM, Adrian Klaver
> <adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)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(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message hubert depesz lubaczewski 2014-08-22 18:14:58 Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Previous Message hubert depesz lubaczewski 2014-08-22 17:51:55 Re: deadlock in single-row select-for-update + update scenario? How could it happen?