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 Jeff Janes
Subject Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Date
Msg-id CAMkU=1y5honjR=VPpsnaY1ZsJRwAsChj=CCu-zhv3ZRHMeWX1A@mail.gmail.com
Whole thread Raw
In response to deadlock in single-row select-for-update + update scenario? How could it happen?  (hubert depesz lubaczewski <depesz@gmail.com>)
Responses Re: deadlock in single-row select-for-update + update scenario? How could it happen?  (hubert depesz lubaczewski <depesz@gmail.com>)
List pgsql-general
Tree view
On Fri, Aug 22, 2014 at 9:29 AM, hubert depesz lubaczewski <depesz@gmail.com> wrote:
I have developer with pg 9.3.5, which is reporing something really strange.

He runs importer, which does, in single transaction:

begin;
select * from table where pkey = <value> limit 1 for update;
update table set ... where pkey = <the same_value>;
commit;

and two backends running the same transaction deadlock.

I checked for duplicated rows with the same pkey value - none are there. And frankly - I'm out of ideas.

What transaction isolation level is being used?

Cheers,

Jeff

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: hubert depesz lubaczewski
Date:
Subject: Re: deadlock in single-row select-for-update + update scenario? How could it happen?