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 Lane||Date: 2001-06-26 13:47:34|
|Subject: Re: stuck spin lock with many concurrent users |
|Previous:||From: Jim Mercer||Date: 2001-06-26 12:56:28|
|Subject: Re: Encrypting pg_shadow passwords|