Marcin Waldowski wrote:
> Magnus Hagander wrote:
>> Tom Lane wrote:
>>
>>> Magnus Hagander <[EMAIL PROTECTED]> writes:
>>>
No, it's definitly the right primitive. But we're creating it with a
max
count of 1.
>>> That's definitely wrong. There are at least three rea
Magnus Hagander wrote:
Tom Lane wrote:
Magnus Hagander <[EMAIL PROTECTED]> writes:
No, it's definitly the right primitive. But we're creating it with a max
count of 1.
That's definitely wrong. There are at least three reasons for a PG
process's semaphore to be signaled (heavywe
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
do
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> How is it possible for a semaphore to be unlocked "too many times"?
>>> It's supposed to be a running counter of the net V's minus P's, and
>>> yes it had better be able to count higher than one. Have we chosen
>>
Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> On Fri, Apr 20, 2007 at 09:20:05AM +0200, Marcin Waldowski wrote:
I've looked at the code there, and can't find a clear problem. One way it
could happen is if the actual PGSemaphoreUnlock() is called once more than
need
Marcin Waldowski wrote:
Doesn't the postmaster restart all other backends due to the FATAL
error?
Are you saying that you can no longer make new connections to the
server,
or is the problem coming from that the aplpication doesn't like that the
server kicked out all connections?
No, we a
Magnus Hagander wrote:
Hmm, PGSemaphoreUnlock() actually ignore this error, only log that it
happens.
No. It does ereport(FATAL) which terminates the backend.
Oh, now I see, sorry :) Indeed on this one connection we receive
exception "FATAL: could not unlock semaphore", after that r
Magnus Hagander wrote:
I've looked at the code there, and can't find a clear problem. One way it
could happen is if the actual PGSemaphoreUnlock() is called once more than
needed.
CC:ing to hackers for this question:
Any chance that's happening? If this happens with SysV semaphores, will
they
