Postgres Pro
Downloads
Home   >   mailing lists

Re: pgbench unable to scale beyond 100 concurrent connections - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pgbench unable to scale beyond 100 concurrent connections
Date
Msg-id CA+TgmoYrWoMbyq7xJUirYuoMVrzVG-ZZ37uLe7zrR6sV2B9+fA@mail.gmail.com
Whole thread Raw
In response to Re: pgbench unable to scale beyond 100 concurrent connections  (Sachin Kotwal <kotsachin@gmail.com>)
List pgsql-hackers
Tree view 
On Wed, Jun 29, 2016 at 8:36 AM, Sachin Kotwal <kotsachin@gmail.com> wrote:
> postgresql does not give any error.
>
> pgbench says:
> client 36 aborted in state 2: ERROR:  could not connect to server "server_1"
> DETAIL:  FATAL:  sorry, too many clients already

The error message that you are seeing there "FATAL: sorry, too many
clients already" is coming from the server.  pgbench is just reporting
the error which the server has sent to it.  Now, it is impossible for
me to know why the server is out of connections, but a likely cause is
that you haven't set max_connections high enough.  If there is some
other cause, you haven't provided enough information to diagnose it.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Strange behavior of some volatile function like random(), nextval()
Next
From: Robert Haas
Date:
Subject: Re: Protocol buffer support for Postgres