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

From: hubert depesz lubaczewski <depesz(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(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-25 11:18:43
Message-ID: CAKrjmhe3+rHUgjAUjQvLiOz55SQ6Fs2qE1PVBOwGaVX3PoYvgw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Aug 22, 2014 at 9:21 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message hubert depesz lubaczewski 2014-08-25 11:37:08 Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Previous Message hubert depesz lubaczewski 2014-08-25 11:17:40 Re: deadlock in single-row select-for-update + update scenario? How could it happen?