From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Steve McWilliams" <smcwilliams(at)EmprisaNetworks(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org, pgsql-hackers-win32(at)postgresql(dot)org |
Subject: | Re: Win32 deadlock detection not working for Postgres8beta1 |
Date: | 2004-09-02 15:55:30 |
Message-ID: | 29909.1094140530@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers-win32 |
"Steve McWilliams" <smcwilliams(at)EmprisaNetworks(dot)com> writes:
> I am just starting to test out Postgres8 beta1 and notice that the
> deadlock detection mechanism is not working (under windows XP pro with
> service pack 1). I am using the version of Postgres built by the
> PGFoundry project, and have it installed as a service.
> To produce the bug I simply launch 2 separate psql windows, begin a
> transaction in each, then do staggered 'SELECT ... FOR UPDATE' calls on 2
> different rows in each of the psql windows, in reverse order. The two
> processes will hang indefinitely.
> The deadlock detection for 8beta1 seems to work fine under linux btw. I
> have not tried this using a version of 8beta1 built using cygwin, but I
> have run versin 7.4 under cygwin before without this problem.
A reasonable theory about this would be that the timer interrupt isn't
firing. Does "statement_timeout" work either?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gaetano Mendola | 2004-09-02 16:05:53 | Re: Sugestion |
Previous Message | Steve McWilliams | 2004-09-02 15:25:55 | Win32 deadlock detection not working for Postgres8beta1 |
From | Date | Subject | |
---|---|---|---|
Next Message | Steve McWilliams | 2004-09-02 16:12:23 | Re: Win32 deadlock detection not working for Postgres8beta1 |
Previous Message | Tom Lane | 2004-09-02 15:46:00 | Re: Compiling beta2 with openssl on XP Pro |