| 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: [PATCHES] [pgsql-hackers-win32] Win32 deadlock detection not working for Postgres8beta1 |
| Date: | 2004-09-06 23:57:42 |
| Message-ID: | 22964.1094515062@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:
> [ 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 semaphore, and so it's not going to be executing
CHECK_FOR_INTERRUPTS at all. How does this fix that case?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-09-07 03:04:56 | Re: Permissions problem with sequences |
| Previous Message | Tom Lane | 2004-09-06 19:33:46 | Re: BUG #1241: returns different result for the same result with differnt plans. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2004-09-07 08:13:53 | Re: [PATCHES] [pgsql-hackers-win32] Win32 deadlock detection not working for Postgres8beta1 |
| Previous Message | Andreas Pflug | 2004-09-06 22:01:56 | Re: VC++ psql build broken |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2004-09-07 04:00:00 | new spanish translations |
| Previous Message | Tom Lane | 2004-09-06 16:48:23 | Re: fix for pg_dump (caused by array output syntax changes) |