>On 12/16/14 17:39, Stephen R. van den Berg wrote: >> Anyway, I just tested the threading problem on 8.0. >> Comparable (fatal) results.
Arne Goedeke wrote: >What exactly does that mean? Is there a threading bug in pike 8 or is >there a threading bug in the new postgres module? In this case it means that there is a threading bug in Pike 8. The new postgres module has been performing quite admirably for the past four weeks in various production systems. Looks stable. I tried rewriting the module slightly to fold back threads into the backend when idle. During that process, I ran into some fundamental threading wierdness in Pike 8.x Since there is no cmod in play here, and the changes are in pike code only, the problem must be in Pike itself. However, in an effort to dig out the bug in Pike, I compiled Pike with various debugging options; which resulted in inconsistent erratic behaviour (even stranger than the original problem), which, to add insult to injury, even varies depending on the debugging level applied. -- Stephen.
