Re: [HACKERS] some problems with new locking code - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] some problems with new locking code
Date
Msg-id 199802241956.OAA14773@candle.pha.pa.us
Whole thread Raw
In response to some problems with new locking code  ("Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su>)
List pgsql-hackers
>
> I created simple table (just single int4 attr) with index on it
> and tried to reproduce reported problems with BTP_CHAIN flag
> (without success, unfortunately ?) by inserting data by 3-4 psql-s
> simultaneously. No problems with 2 clients. But when 3rd psql
> starts one of psql-s becomes blocked for long time (a minutes).
> After some time blocked process may continue insertion but
> another process is sleeping instead of wake-uped proc. The same
> with 4 psql-s: one of process is always sleeping!

Thanks for finding this, Vadim.  I had meant to re-run my locking tests
on the new code before the 6.3 final, but had not done it yet.  I ran
them now, and they didn't work as they should.  It is fixed now.

The problem was that I was incrementing a counter in a while conditional
test, even though I was not executing the loop, and the counter was used
in the next loop.

--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh'
Next
From: Peter T Mount
Date:
Subject: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh'