Search Postgresql Archives
Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
From
: Andrej Vanek <
andrej.vanek.sk@xxxxxxxxx
>
Date
: Fri, 3 Oct 2014 11:36:52 +0200
Cc
: Bill Moran <
wmoran@xxxxxxxxxxxxxxxxx
>, pgsql-general <
pgsql-general@xxxxxxxxxxxxxx
>
In-reply-to
: <
20140925140502.GX5311@eldon.alvh.no-ip.org
>
Hi,
retested:
yes, this is still an issue in 9.3.5, same deadlock errors occured.
Do you need to extract some simplified reproducible testcase?
Best Regards, Andrej
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
References
:
deadlock of lock-waits (on transaction and on tuple) using same update statement
From:
Andrej Vanek
Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
From:
Bill Moran
Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
From:
Andrej Vanek
Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
From:
Andrej Vanek
Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
From:
Alvaro Herrera
Prev by Date:
Re: Getting my Database name in a C Extension
Next by Date:
Re: Getting my Database name in a C Extension
Previous by thread:
Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
Next by thread:
which Update quicker
Index(es):
Date
Thread
[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]
