Re: BUG #15661: Error connecting to the server

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: youssef(dot)zrirak(at)yazaki-europe(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15661: Error connecting to the server
Date: 2019-02-28 14:28:20
Message-ID: CAKFQuwYQjmgXFuW6oL94pKxp51t+UQMYXY0NXQjFv8nrq8m0dg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Feb 28, 2019 at 3:22 AM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 15661
> Logged by: ZRIRAK YOUSSEF
> Email address: youssef(dot)zrirak(at)yazaki-europe(dot)com
> PostgreSQL version: 9.4.0
> Operating system: windows server 2012 R2
> Description:
>
> Hello
> we had faced many type this type of message ( Error connecting to the server
> :Fatal: too many clients already )
>
> could you please support in this subject

This is not a bug. You either need to increase max_connections or
decrease the number of simultaneous connections.

David J.

p.s. if you didn't just choose a version randomly you really need to
put "updating and upgrading PostgreSQL" into the list of DBA tasks
that your system needs performed regularly.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-02-28 17:30:48 Re: BUG #15660: pg_dump memory leaks when dumping LOBs
Previous Message Dean Rasheed 2019-02-28 14:07:46 Re: BUG #15623: Inconsistent use of default for updatable view