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

From: hubert depesz lubaczewski <depesz(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(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:36:34
Message-ID: CAKrjmhd34dzZrStCC9A3LZucWTEFNtiYBSuii08kOuY6H9wKAg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Aug 22, 2014 at 7:20 PM, Adrian Klaver <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.

depesz

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2014-08-22 17:43:00 Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Previous Message hubert depesz lubaczewski 2014-08-22 17:35:14 Re: deadlock in single-row select-for-update + update scenario? How could it happen?