From: | Lew <noone(at)lwsc(dot)ehost-services(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Connection Pooling |
Date: | 2010-04-03 17:47:50 |
Message-ID: | hp7v07$9iv$1@news.albasani.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
John R Pierce wrote:
>> for that matter, JDBC has its own connection pooling in java.
David Kerr wrote:
> It looks like both of those solutions require a coding change. I'm
> hoping for a middleware solution similar to pgpool/pgbouncer.
How's that?
If JDBC has its own connection pooling and you're already using JDBC, voilà!
no change needed, right?
If you're using a DataSource for JDBC, then it's a configuration change, not a
code change, to switch to different databases, including to a different brand
like Oracle instead of PG, never mind to switch between a pooled or unpooled
connection.
Most app servers, including Tomcat, provide DBCP inbuilt with no further
effort on the programmer's or even the deployer's part.
So to what coding changes do you refer?
--
Lew
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2010-04-03 18:58:36 | Re: How to implement word wrap |
Previous Message | Tom Lane | 2010-04-03 17:05:09 | Re: ERROR: cache lookup failed for relation X |