| From: | Daniele Depetrini <daniele(dot)depetrini(at)criticalpath(dot)net> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Pooled connections idle timeout |
| Date: | 2008-08-22 12:11:29 |
| Message-ID: | 48AEACF1.3030606@criticalpath.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Oliver Jowett wrote:
> Daniele Depetrini wrote:
>> Hi Again,
>>
>> Any ideas?
>
> There is no auto-idle-close mechanism in the pool implementation
> provided by the driver.
>
> The connection pool shipped with the driver is very basic. If it
> doesn't do what you need it to, you probably want to use a 3rd party
> connection pool (e.g. dbcp). I don't think there's much point in
> building any sort of fully-featured connection pool to ship with the
> driver - there are plenty of other implementations already out there.
>
> -O
>
>
Thanks for the answer. Actually according to my testing up to now is
working "well enough". It's not clear to me if prepared statements
pooling is implemented: in positive case will be much better to use
internal pooling instead of an external one, what do you think?
Daniele.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2008-08-22 23:23:47 | Re: Error selecting constant |
| Previous Message | Thomas Markus | 2008-08-22 11:12:37 | Re: Tracing SQL statements per page/request |