Re: max_connections reached in postgres 9.3.3 - Mailing list pgsql-general

From Merlin Moncure
Subject Re: max_connections reached in postgres 9.3.3
Date
Msg-id CAHyXU0zyZsg8TiZ7ZByiLk2kqUGS8SspcCmwceunrDt3zGXV8g@mail.gmail.com
Whole thread Raw
In response to Re: max_connections reached in postgres 9.3.3  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: max_connections reached in postgres 9.3.3
List pgsql-general
On Thu, Jun 12, 2014 at 3:32 PM, Kevin Grittner <kgrittn@ymail.com> wrote:
> Merlin Moncure <mmoncure@gmail.com> wrote:
>
>> or something else entirely.
>
>
> It strikes me that this might be relevant:

Agreed.  The stock advice to many, many problems of this sort is 'use
pgbouncer' but it can be hard to work in a lot of code bases and we
have to be careful to rule out some underlying possible contributing
factors before switching up things up to much.  THP compaction in
particular has plaguing servers throughout the company I work for; we
haven't figured out OP's system went loaded all of a sudden.
Nevertheless, having a setup that can accumulate 1000's of connections
during high load events is not the way to go.  Other than pgbouncer,
being very spartan with application server connection pools can bring
benefits (but can also cause problems).

merlin


pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: Spurious Stalls
Next
From: Eric Ridge
Date:
Subject: Memory leak with CREATE TEMP TABLE ON COMMIT DROP?