| Lists: | pgsql-jdbc |
|---|
| From: | Antonini Roberto <Roberto(dot)Antonini(at)TILAB(dot)COM> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | JDBC driver |
| Date: | 2004-06-29 12:45:44 |
| Message-ID: | 6ECEC1E214F2E342814ABB1ED10E7955F9974B@EXC2K01B.cselt.it |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-jdbc |
Hi all,
I'm a newbie in this mailing list.
I'm using a JDBC driver to access a postgres DB, the version of my jar
is 7.2,
I get some performance troubles using this driver in a sense of CPU
consuming.
Could someone help me, suggesting me a best-performance JDBC driver?
Roby.
Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
====================================================================
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin(at)tilab(dot)com(dot) Thank you
====================================================================
| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Antonini Roberto <Roberto(dot)Antonini(at)TILAB(dot)COM> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: JDBC driver |
| Date: | 2004-07-01 08:15:27 |
| Message-ID: | Pine.BSO.4.56.0407010312540.2807@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-jdbc |
On Tue, 29 Jun 2004, Antonini Roberto wrote:
> I get some performance troubles using this driver in a sense of CPU
> consuming.
>
> Could someone help me, suggesting me a best-performance JDBC driver?
>
You haven't really described what you are doing or what is consuming the
CPU. Are you having a problem with a query taking to long on the server
or is your complaint specifically about the JDBC driver itself consuming a
lot of CPU? More details please.
Kris Jurka