| From: | Igor Neyman <ineyman(at)perceptron(dot)com> |
|---|---|
| To: | Viktor <viktor(at)okservers(dot)eu>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Random server overload |
| Date: | 2013-10-02 13:34:29 |
| Message-ID: | A76B25F2823E954C9E45E32FA49D70EC4282408F@mail.corp.perceptron.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> -----Original Message-----
> From: pgsql-admin-owner(at)postgresql(dot)org [mailto:pgsql-admin-
> owner(at)postgresql(dot)org] On Behalf Of Viktor
> Sent: Wednesday, October 02, 2013 4:12 AM
> To: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] Random server overload
>
> On 10/1/2013 4:45 PM, Igor Neyman wrote:
> > Did you try using any kind of connection pooler, e.g. PgBouncer?
> > Should help.
>
> Our Java application uses c3p0 connection pooler and we don't think that it's
> the issue.
>
>
"Client-side" connection pooling is different from server-side (such as PgBouncer), and I believe is not as effective as PgBouncer.
As you stated in original message you have multiple idle connections, that's waste of resources.
Regards,
Igor Neyman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergey Klochkov | 2013-10-02 14:44:51 | Re: PostgreSQL 9.2 - pg_dump out of memory when backuping a database with 300000000 large objects |
| Previous Message | Nikolay Morozov | 2013-10-02 08:20:34 | Database replication to 50-80 nodes |