From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Suprabhat <suprabhatm@gmail.com>
To: pgsql-bugs@postgresql.org
Subject: Re: BUG #5995: connection pooling not working
Date: Wed, 27 Apr 2011 08:44:37 -0500
Message-ID: <4DB7D775020000250003CF28@gw.wicourts.gov> (raw)
In-Reply-To: <201104271155.p3RBtDwu092291@wwwmaster.postgresql.org>
References: <201104271155.p3RBtDwu092291@wwwmaster.postgresql.org>
"Suprabhat" <suprabhatm@gmail.com> wrote:
> FATAL: too many connections already and there are too many
> postgres processes on the server. We have used connection
> pooling methods after unsuccessfully using pgpool2.
Is there a thread somewhere where you were trying to get help
configuring pgpool?
> Probably we are doing some basics wrong.
>
> Total number of connections we are trying to make is something
> around 300 concurrently.
Well, the main point of a connection pool is to allow multiple
client-side processes or threads to see a large number of logical
connections to the database while those funnel down to a small
number on the database side. 300 active users might do quite well
on a connection pool which maintains 10 or 20 connections to the
database. It sounds like you haven't used the correct settings to
achieve that.
-Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, suprabhatm@gmail.com, pgsql-bugs@postgresql.org
Subject: Re: BUG #5995: connection pooling not working
In-Reply-To: <4DB7D775020000250003CF28@gw.wicourts.gov>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox