| From: | "Wappler, Robert" <rwappler(at)ophardt(dot)com> |
|---|---|
| To: | "David Kerr" <dmk(at)mr-paradox(dot)net>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Connection Pooling |
| Date: | 2010-03-29 07:34:52 |
| Message-ID: | C8E2DAF0E663A948840B04023E0DE32A026C0F98@w2k3server02.de.ophardt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2010-03-29, David Kerr wrote:
> On 3/27/2010 12:46 AM, John R Pierce wrote:
>> Allan Kamau wrote:
>>> You may also have a look at Commons DBCP from Apache software
>>> foundation, "http://commons.apache.org/dbcp/". I have used it for a
>>> few projects and have had no problems.
>>
>> for that matter, JDBC has its own connection pooling in java.
>>
>>
>>
>
> It looks like both of those solutions require a coding change. I'm
> hoping for a middleware solution similar to pgpool/pgbouncer.
>
I'm using proxool for JDBC-connection pooling. It behaves as a usual
JDBC-Driver or DataSource should do. The configuration can be loaded
statically when starting the application.
--
Robert...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frans Hals | 2010-03-29 07:39:35 | Re: Large index operation crashes postgres |
| Previous Message | Faheem Mitha | 2010-03-29 06:43:30 | Re: simultaneously reducing both memory usage and runtime for a query |