Re: [HACKERS] Re: BUG #3242: FATAL: could not unlock semaphore: error code 298 - Mailing list pgsql-bugs

From Andrew Dunstan
Subject Re: [HACKERS] Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Date
Msg-id 4628F9A7.70200@dunslane.net
Whole thread Raw
In response to Re: BUG #3242: FATAL: could not unlock semaphore: error code 298  (Magnus Hagander <magnus@hagander.net>)
List pgsql-bugs
Magnus Hagander wrote:
>>
>> The effective max count on Unixen is typically in the thousands,
>> and I'd suggest the same on Windows unless there's some efficiency
>> reason to keep it small (in which case, maybe ten would do).
>>     
>
> AFAIK there's no problem with huge numbers (it takes an int32, and the
> documentation says nothing about a limit - I'm sure it's just a 32-bit
> counter in the kernel). I'll give that a shot.
>
>   

Linux manpage suggests local max is 32767, so that's probably a good 
value to try.

cheers

andrew


pgsql-bugs by date:

Previous
From: "Andreas"
Date:
Subject: BUG #3246: User "name" could not be created.
Next
From: "Dorochevsky,Michel"
Date:
Subject: Re: BUG #3245: PANIC: failed to re-find shared lock ob ject