Re: [HACKERS] stuck spin lock with many concurrent users

[Tom Lane]

Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> It appeared that the deadlock checking timer seems to be the source of
> the problem. With the default settings, it checks deadlocks every 1
> second PER backend.

I don't believe it.  setitimer with it_interval = 0 should produce one
interrupt, no more.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://www.postgresql.org/search.mpl