Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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


--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux