Re: pgbench unable to scale beyond 100 concurrent connections

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Sachin Kotwal <kotsachin(at)gmail(dot)com>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgbench unable to scale beyond 100 concurrent connections
Date: 2016-06-29 15:14:59
Message-ID: CA+TgmoYrWoMbyq7xJUirYuoMVrzVG-ZZ37uLe7zrR6sV2B9+fA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 29, 2016 at 8:36 AM, Sachin Kotwal <kotsachin(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-06-29 15:30:43 Re: Protocol buffer support for Postgres
Previous Message Tom Lane 2016-06-29 15:04:51 Re: Strange behavior of some volatile function like random(), nextval()