> > [ fix broken CHECK_FOR_INTERRUPTS macro ]
>
> 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 semaphor
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> How does this fix that case?
> It doesn't. This is why the second version of the patch was required,
> per http://archives.postgresql.org/pgsql-patches/2004-09/msg00039.php.
Okay, I've applied the right version of the patch now ;-)
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> [ fix broken CHECK_FOR_INTERRUPTS macro ]
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 goin
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> A reasonable theory about this would be that the timer interrupt isn't
>> firing. Does "statement_timeout" work either?
> Bugger. I've found the reason for this - statement_timeout was also
> broken. This was broken by the change of how signals are
> "Steve McWilliams" <[EMAIL PROTECTED]> writes:
>> I am just starting to test out Postgres8 beta1 and notice that the
>> deadlock detection mechanism is not working (under windows XP pro with
>> service pack 1). I am using the version of Postgres built by the
>> PGFoundry project, and have it in
"Steve McWilliams" <[EMAIL PROTECTED]> writes:
> I am just starting to test out Postgres8 beta1 and notice that the
> deadlock detection mechanism is not working (under windows XP pro with
> service pack 1). I am using the version of Postgres built by the
> PGFoundry project, and have it installed
Hello,
I am just starting to test out Postgres8 beta1 and notice that the
deadlock detection mechanism is not working (under windows XP pro with
service pack 1). I am using the version of Postgres built by the
PGFoundry project, and have it installed as a service.
To produce the bug I simply lau
