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

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: hubert depesz lubaczewski <depesz(at)gmail(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-22 17:43:00
Message-ID: 53F78124.3090702@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 08/22/2014 10:36 AM, hubert depesz lubaczewski wrote:
> On Fri, Aug 22, 2014 at 7:20 PM, Adrian Klaver
> <adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)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(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2014-08-22 17:49:56 Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Previous Message hubert depesz lubaczewski 2014-08-22 17:36:34 Re: deadlock in single-row select-for-update + update scenario? How could it happen?