From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
Cc: | "Steve McWilliams" <smcwilliams(at)EmprisaNetworks(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers-win32(at)postgresql(dot)org, "PostgreSQL-patches" <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [pgsql-hackers-win32] Win32 deadlock detection not working for Postgres8beta1 |
Date: | 2004-09-02 19:07:22 |
Message-ID: | 21331.1094152042@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers-win32 pgsql-patches |
"Magnus Hagander" <mha(at)sollentuna(dot)net> 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 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 ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Claudio Natoli | 2004-09-03 01:10:37 | Re: [pgsql-hackers-win32] Win32 deadlock detection not wor |
Previous Message | Magnus Hagander | 2004-09-02 18:40:34 | Re: [BUGS] Win32 deadlock detection not working for Postgres8beta1 |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2004-09-02 19:22:35 | Re: [BUGS] Win32 deadlock detection not working for Postgres8beta1 |
Previous Message | Magnus Hagander | 2004-09-02 18:59:34 | Re: [BUGS] Win32 deadlock detection not working for Postgres8beta1 |
From | Date | Subject | |
---|---|---|---|
Next Message | Claudio Natoli | 2004-09-03 01:10:37 | Re: [pgsql-hackers-win32] Win32 deadlock detection not wor |
Previous Message | Magnus Hagander | 2004-09-02 18:59:34 | Re: [BUGS] Win32 deadlock detection not working for Postgres8beta1 |