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

Re: [HACKERS] Re: BUG #3242: FATAL: could not unlock semaphore: error code 298

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marcin Waldowski <M(dot)Waldowski(at)sulechow(dot)net>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Re: BUG #3242: FATAL: could not unlock semaphore: error code 298
Date: 2007-04-20 17:34:31
Message-ID: 4628F9A7.70200@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
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

In response to

pgsql-hackers by date

Next:From: Neil ConwayDate: 2007-04-20 17:45:58
Subject: Re: Improving deadlock error messages
Previous:From: Magnus HaganderDate: 2007-04-20 17:01:06
Subject: Re: BUG #3242: FATAL: could not unlock semaphore: error code 298

pgsql-bugs by date

Next:From: Dorochevsky,MichelDate: 2007-04-21 16:30:02
Subject: Re: BUG #3245: PANIC: failed to re-find shared lock object
Previous:From: Magnus HaganderDate: 2007-04-20 17:01:06
Subject: Re: BUG #3242: FATAL: could not unlock semaphore: error code 298

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