From: | Yetkin Öztürk <yetkin85(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: connection poolers' db connections |
Date: | 2013-02-13 15:35:40 |
Message-ID: | CALL033DqJwxuQX6Xe-4-iLd5MZyEVoyNdwCGvS9DDQSk+2_PYQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi Kevin,
thanks for responding. I understand its a world of bottlenecks, different
combinations of producer-consumer problems,
Beyond a certain point, starting the query sooner will cause it to
> finish later. Really.
but I think in our situation our Postgres server can consume more
connections, at least i'll give a try.
Yetkin.
2013/2/13 Kevin Grittner <kgrittn(at)ymail(dot)com>
> Yetkin Öztürk <yetkin85(at)gmail(dot)com> wrote:
>
> > Which key should i set for changing the limit of connection
> > between pgbouncer <-> posgres8.4?
>
> The options which end in _pool_size. max_client_conn specifies how
> many application connections can be made to pgbouncer.
>
> It's generally best to use pool_mode of transaction if you can.
>
> > I want to increase the connections of pgbouncer opened on posgres
> > (pgbouncer<->posgres) to eliminate waiting connections in the
> > pool, to consume queries faster.
>
> Be sure to read this:
>
> http://wiki.postgresql.org/wiki/Number_Of_Database_Connections
>
> Beyond a certain point, starting the query sooner will cause it to
> finish later. Really.
>
>
> --
> Kevin Grittner
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2013-02-13 19:24:41 | Re: High CPU usage / load average after upgrading to Ubuntu 12.04 |
Previous Message | Kevin Grittner | 2013-02-13 14:56:54 | Re: connection poolers' db connections |