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 Adrian Klaver
Subject Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Date
Msg-id 53F78124.3090702@aklaver.com
Whole thread Raw
In response to Re: 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?
List pgsql-general
Tree view 
On 08/22/2014 10:36 AM, hubert depesz lubaczewski wrote:
> On Fri, Aug 22, 2014 at 7:20 PM, Adrian Klaver
> <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:
>
>     So why are different processes running the exact same queries coming
>     in on different ports?
>
>
> the importer is parallelized, and sometimes two processes handle batches
> of data that happen to update the same "top level row".
>
> but the deadlocking problem is happening only on one machine, though
> very repeatably.

Which begs the question, what is different about that machine?

>
> depesz


--
Adrian Klaver
adrian.klaver@aklaver.com

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