Re: [HACKERS] Re: Anyone understand shared-memory space usage? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Re: Anyone understand shared-memory space usage?
Date
Msg-id 11301.919782315@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Re: Anyone understand shared-memory space usage?  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <maillist@candle.pha.pa.us> writes:
>> I think it's entirely likely that this set of bugs can account for flaky
>> behavior seen in installations with more than 256 shared-memory buffers
>> (postmaster -B > 256), more than 256 simultaneously held locks (have no
>> idea how to translate that into user terms), or more than 256 concurrent
>> backends.  I'm still wondering whether that might describe Daryl
>> Dunbar's problem with locks not getting released, for example.

> People have reported sloness/bugs with hash index lookups.  Does this
> relate to that?

It looks like the routines in src/backend/access/hash/ don't use the
code in src/backend/utils/hash/ at all, so my guess is that whatever
bugs might lurk in hash indexes are unrelated.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Philip Shiels
Date:
Subject: Alterations to backend/client protocol
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] copyObject() ?