>>> A reasonable theory about this would be that the timer
>>> 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
>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)
pgsql-hackers-win32 by date
|Next:||From: Tom Lane||Date: 2004-09-02 19:53:18|
|Subject: Re: [BUGS] Win32 deadlock detection not working for Postgres8beta1 |
|Previous:||From: Tom Lane||Date: 2004-09-02 19:07:22|
|Subject: Re: [pgsql-hackers-win32] Win32 deadlock detection not working for Postgres8beta1 |