| From: | Hilmar Lapp <hlapp(at)gmx(dot)net> |
|---|---|
| To: | "Charles H(dot) Woloszynski" <chw(at)clearmetrix(dot)com> |
| Cc: | Jeff <threshar(at)torgo(dot)978(dot)org>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: join over 12 tables takes 3 secs to plan |
| Date: | 2003-01-03 22:22:49 |
| Message-ID: | E498D78B-1F69-11D7-AE5F-000393B4BFF6@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc pgsql-performance |
On Friday, January 3, 2003, at 02:16 PM, Charles H. Woloszynski wrote:
> Also, you need to retain the PreparedStatement, it is not cached based
> based on the text of the
> statement, but associated with the PreparedStatement itself
I think that's normal. I don't recall the JDBC spec saying that you
have a chance the server will remember that you created a
PreparedStatement for the same query text before. You have to cache the
PreparedStatement object in your app, not the query string.
BTW that's the same for perl/DBI. At least for Oracle.
-hilmar
--
-------------------------------------------------------------
Hilmar Lapp email: lapp at gnf.org
GNF, San Diego, Ca. 92121 phone: +1-858-812-1757
-------------------------------------------------------------
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Bruce Lynes | 2003-01-04 00:24:26 | Re: Unable to download/compile postgresql.jar for PG 7.3 with JDK 1.4.1 |
| Previous Message | Charles H. Woloszynski | 2003-01-03 22:16:32 | Re: [PERFORM] join over 12 tables takes 3 secs to plan |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albert Cervera Areny | 2003-01-04 13:31:51 | Fwd: Stock update like application |
| Previous Message | Charles H. Woloszynski | 2003-01-03 22:16:32 | Re: [PERFORM] join over 12 tables takes 3 secs to plan |