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 CAKrjmhe3+rHUgjAUjQvLiOz55SQ6Fs2qE1PVBOwGaVX3PoYvgw@mail.gmail.com
Whole thread Raw
In response to Re: deadlock in single-row select-for-update + update scenario? How could it happen?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: deadlock in single-row select-for-update + update scenario? How could it happen?
List pgsql-general
Tree view
On Fri, Aug 22, 2014 at 9:21 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
FWIW this problem was reported also by Andrew Sackville-West at
http://www.postgresql.org/message-id/20140731233051.GN17765@andrew-ThinkPad-X230
I strongly suspect now that the problem is related to the locking of
updated versions as heap_lock_tuple_updated, and perhaps the internal
locking done by EvalPlanQual.  Haven't traced through it.

Is there anything I could tell the developer to do (he's on Mac) so he could provide more information?

depesz

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?