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 hubert depesz lubaczewski
Subject Re: deadlock in single-row select-for-update + update scenario? How could it happen?
Date
Msg-id CAKrjmhd34dzZrStCC9A3LZucWTEFNtiYBSuii08kOuY6H9wKAg@mail.gmail.com
Whole thread Raw
In response to Re: deadlock in single-row select-for-update + update scenario? How could it happen?  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: deadlock in single-row select-for-update + update scenario? How could it happen?  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
Tree view
On Fri, Aug 22, 2014 at 7:20 PM, Adrian Klaver <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.

depesz

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