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 hubert depesz lubaczewski
Subject Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Date
Msg-id CAKrjmhea_M7hkvtxWqch=WwXqWOFpU_POYkyWus-=YLqSj=9vA@mail.gmail.com
Whole thread Raw
In response to Re: deadlock in single-row select-for-update + update scenario? How could it happen?  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: deadlock in single-row select-for-update + update scenario? How could it happen?  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
Tree view
On Fri, Aug 22, 2014 at 7:43 PM, Adrian Klaver <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.

depesz

pgsql-general by date:

Previous
From: Tom Lane
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?