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

From: hubert depesz lubaczewski <depesz(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(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:50:44
Message-ID: CAKrjmhea_M7hkvtxWqch=WwXqWOFpU_POYkyWus-=YLqSj=9vA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Aug 22, 2014 at 7:43 PM, Adrian Klaver <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.

depesz

In response to

Responses

Browse pgsql-general by date

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