"Magnus Hagander" <mha (AT) sollentuna (DOT) net> writes:
Applied. I see how this might change detection of statement_timeout,
but I do not actually see what it's got to do with deadlock detection.
In the deadlock situation the process that needs to wake up is going
to be blocked on a semaphore, and so it's not going to be executing
CHECK_FOR_INTERRUPTS at all. How does this fix that case?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

"Magnus Hagander" <mha (AT) sollentuna (DOT) net> writes:
Okay, I've applied the right version of the patch now ;-)

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org

It doesn't. This is why the second version of the patch was required,
per http://archives.postgresql.org/pgsql...9/msg00039.php.
It even specifically says this is so it fixes the deadlock issues and
not just statement_timeout :-)


//Magnus

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org