| From: | "Nick Fankhauser" <nickf(at)ontko(dot)com> |
|---|---|
| To: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
| Cc: | "A(dot)M(dot)" <agentm(at)cmu(dot)edu>, <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: FATAL 1: Sorry, too many clients already |
| Date: | 2002-11-08 18:45:43 |
| Message-ID: | NEBBLAAHGLEEPCGOBHDGMEEGGCAA.nickf@ontko.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
>> If you aren't using pooled
>> connections, maybe you just have more users on the web.
>
> But is there really that number of backends/connections present?
Assuming there is no connection pooling going on, then yes, it is reasonable
to assume that more users means more connections. (I don't know whether DBI
has pooling built-in.)
> I see that error message in storage/ipc/sinval.c (7.2.3) so it
> could be some
> sort kernel limit on shared memory connections or something like that.
Nope, this is definitely a message from the postgresql backend. I'm
embarrassed to admit how many times I've seen it....
FATAL 1: Sorry, too many clients already
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nick Fankhauser | 2002-11-08 18:50:41 | typo RE: FATAL 1: Sorry, too many clients already |
| Previous Message | Nigel J. Andrews | 2002-11-08 18:43:34 | Re: FATAL 1: Sorry, too many clients already |