Thread: Re: [BUGS] Win32 deadlock detection not working for Postgres8beta1

>>> 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 handled on
>> win32.
>
>Just outta curiosity, why wasn't that detected by the regression tests?
>There is a test that depends on statement_timeout working ...

Very good question :-)

This is the plpgsql test? (quick grep) Has it been changed recently?
It's been a while since I ran the full regression tests, due to a broken
setup. (it passes fine now)

//Magnus

"Magnus Hagander" <mha@sollentuna.net> writes:
>> Just outta curiosity, why wasn't that detected by the regression tests?
>> There is a test that depends on statement_timeout working ...

> Very good question :-)

> This is the plpgsql test? (quick grep) Has it been changed recently?

Um, whenever I put in the plpgsql exception support, which was end of
July I think.

            regards, tom lane