Re: cannot detect too many clients

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: cannot detect too many clients
Date: 2001-09-06 03:05:21
Message-ID: 29257.999745521@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
>> I have a fatal error message while connecting more than 32 users using
>> current:
>> Aug 29 11:25:18 srapc1474 postgres[12189]: [1] FATAL 1:
>> ProcGetNewSemIdAndNum: cannot allocate a free semaphore
>> rather than a more informative message:
>> Sorry, too many clients already
>> Does anynbody know what's happening?

> Ugh. I thought I'd tested that.

Indeed I had, but I'd used a low value of MaxBackends to test it.
If MaxBackends is a multiple of PROC_NSEMS_PER_SET (16) then too-many-
backends will be detected here, not later on when we try to insert our
PROC entry into the sinval array. Whoops. Fix committed.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-09-06 03:19:45 Re: Log rotation?
Previous Message Bruce Momjian 2001-09-06 02:51:57 Re: [PATCH] Win32 errno a little bit safer