From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Jeffery Collins <collins(at)onyx-technologies(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Connection problem under extreme load. |
Date: | 2000-07-28 04:47:17 |
Message-ID: | 39811055.AA513CCE@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> We have been doing some load testing with postgresql, and we have been
> getting the following error when libpq attempts to connect to the
> backend. This only happens occasionally and, as I said under extreme
> load (e.g. load average 30+ on a single processor Sun).
> connectDBStart() -- connect() failed: Connection refused
> Is the postmaster running at 'localhost' and accepting connections on
> Unix socket '6700'?
> Has anyone seen this before or know what could be happening? One theory
> that we have is that the connection request timed out because the server
> was under such heavy load that it couldn't respond to the request. Is
> this possible?
You are increasing the number of allowed connections to above 32, right?
The runtime default is 32, but it can be increased with a commandline
switch.
- Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-07-28 05:38:41 | Re: pg_dump error |
Previous Message | Thomas Swan | 2000-07-28 04:47:00 | Re[2]: upgrade from 6.4 to 7.02 problem |