Skip site navigation (1) Skip section navigation (2)

Re: stuck spin lock with many concurrent users

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: stuck spin lock with many concurrent users
Date: 2001-06-26 13:42:11
Message-ID: 2790.993562931@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)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

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-06-26 13:47:34
Subject: Re: stuck spin lock with many concurrent users
Previous:From: Jim MercerDate: 2001-06-26 12:56:28
Subject: Re: Encrypting pg_shadow passwords

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group