"Steve McWilliams" <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
