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

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-03 18:22:03
Message-ID: 5629.999541323@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
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.  The problem is that it runs out of
semaphores before noting that there's no free slots in the PROC array
(which is where the "more informative" message was supposed to come
out).  Need to rearrange the order of operations, or some such.
Will fix.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Colin 't HartDate: 2001-09-03 18:30:11
Subject: Re: Porting to Native WindowsNT/2000
Previous:From: Peter EisentrautDate: 2001-09-03 17:57:37
Subject: Re: INDEX BUG???

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