Re: Random server overload

Поиск
Список
Период
Сортировка
От Igor Neyman
Тема Re: Random server overload
Дата
Msg-id A76B25F2823E954C9E45E32FA49D70EC4282408F@mail.corp.perceptron.com
обсуждение исходный текст
Ответ на Re: Random server overload  (Viktor <viktor@okservers.eu>)
Ответы Re: Random server overload  (Kevin Grittner <kgrittn@ymail.com>)
Список 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 по дате отправления:

Предыдущее
От: Nikolay Morozov
Дата:
Сообщение: Database replication to 50-80 nodes
Следующее
От: Sergey Klochkov
Дата:
Сообщение: Re: PostgreSQL 9.2 - pg_dump out of memory when backuping a database with 300000000 large objects