From: | "Marko Kreen" <markokr(at)gmail(dot)com> |
---|---|
To: | dmitry(at)koterov(dot)ru |
Cc: | "Postgres General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Sthange things happen: SkyTools pgbouncer is NOT a balancer |
Date: | 2007-09-11 17:29:39 |
Message-ID: | e51f66da0709111029o5e5a7c56wea08b62e65ec706a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 9/11/07, Dmitry Koterov <dmitry(at)koterov(dot)ru> wrote:
> We discovered some time ago that pgbouncer is NOT a balancer, because it
> cannot spread connections/queries to the same database to multiple servers.
> It's unbeliveable, but it's a fact! So, database name in the config MUST be
> unique.
Indeed, pgbouncer is just a connection pooler, not load balancer.
There has been some talk about adding load balancing to it, but
as it can be done as well in network level, I don't see much
point.
> So, it's completely magical for me why "Session pooling", "Transaction
> pooling" and "Statement pooling" options are exist (see
> https://developer.skype.com/SkypeGarage/DbProjects/PgBouncer).
> If pgbouncer is not a balancer, what purpose is to use "Statement pooling" -
> if we sent 100 queries (e.g.) in the same connection, they will always be
> directed to the SAME MACHINE in its different connections, no balancing
> optimization at all.
To use less connections on server side.
--
marko
From | Date | Subject | |
---|---|---|---|
Next Message | hubert depesz lubaczewski | 2007-09-11 18:17:34 | Re: Sthange things happen: SkyTools pgbouncer is NOT a balancer |
Previous Message | Ivan Zolotukhin | 2007-09-11 17:26:11 | Re: Sthange things happen: SkyTools pgbouncer is NOT a balancer |