| From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers-win32(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] Win32 deadlock detection not working for Postgres8beta1 |
| Date: | 2004-09-02 19:22:35 |
| Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE4569DD@algol.sollentuna.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-win32 |
>>> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-09-02 19:53:18 | Re: [BUGS] Win32 deadlock detection not working for Postgres8beta1 |
| Previous Message | Tom Lane | 2004-09-02 19:07:22 | Re: [pgsql-hackers-win32] Win32 deadlock detection not working for Postgres8beta1 |