Re: Random server overload - Mailing list pgsql-admin

From Igor Neyman
Subject Re: Random server overload
Date
Msg-id A76B25F2823E954C9E45E32FA49D70EC4282408F@mail.corp.perceptron.com
Whole thread Raw
In response to Re: Random server overload  (Viktor <viktor@okservers.eu>)
Responses Re: Random server overload
List pgsql-admin

> -----Original Message-----
> From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-
> owner@postgresql.org] On Behalf Of Viktor
> Sent: Wednesday, October 02, 2013 4:12 AM
> To: pgsql-admin@postgresql.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
asPgBouncer. 
As you stated in original message you have multiple idle connections, that's waste of resources.

Regards,
Igor Neyman


pgsql-admin by date:

Previous
From: Nikolay Morozov
Date:
Subject: Database replication to 50-80 nodes
Next
From: Sergey Klochkov
Date:
Subject: Re: PostgreSQL 9.2 - pg_dump out of memory when backuping a database with 300000000 large objects