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 CAKrjmhcW97_Mivy-5-JuUXExgJ3ZOXLJeE3G5B5x_Xpe8tK+Lw@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:54 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
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?

All locally, but hey - how could network latency be a problem? Transaction gets the lock on row, and then it updates. the same row. in the same transaction. with nothing else in the transaction. where is here place for deadlock for another, identical transaction?

depesz

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Next
From: Jerry Sievers
Date:
Subject: Re: Restart replicated slave procedure