Re: stuck spin lock with many concurrent users - Mailing list pgsql-hackers

From Tom Lane
Subject Re: stuck spin lock with many concurrent users
Date
Msg-id 2790.993562931@sss.pgh.pa.us
Whole thread Raw
In response to Re: stuck spin lock with many concurrent users  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-hackers
Tatsuo Ishii <t-ishii@sra.co.jp> 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


pgsql-hackers by date:

Previous
From: Jim Mercer
Date:
Subject: Re: Encrypting pg_shadow passwords
Next
From: Tom Lane
Date:
Subject: Re: stuck spin lock with many concurrent users