| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Explanantion on pgbouncer please |
| Date: | 2013-10-31 16:19:05 |
| Message-ID: | 527282F9.80906@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/31/2013 7:38 AM, Adam Brusselback wrote:
>
> If it is from your app to PGBouncer, that sounds strange, and like the
> app is not properly releasing connections as it should. If it is from
> PGBouncer to PostgreSQL, that sounds normal. I haven't used
> PGBouncer, but i've used other connection poolers in the past. They
> would start out with a set number of minimum connections, and scale up
> to the max number specified as needed. The pooler wouldn't release a
> connection to the DB once it has made one, and just kept it available
> in the pool.
except, there's no way a single web page access should be using 70 or 80
connections. 2-3, ok, maybe.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2013-10-31 16:32:01 | Re: Table with Field Serial - Problem |
| Previous Message | John R Pierce | 2013-10-31 16:15:28 | Re: Connection pooling |