| From: | Mark Kirkwood <markir(at)coretech(dot)co(dot)nz> |
|---|---|
| To: | Bill Chandler <billybobc1210(at)yahoo(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Terrible performance after deleting/recreating indexes |
| Date: | 2004-07-09 00:14:32 |
| Message-ID: | 40EDE368.90603@coretech.co.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc pgsql-performance |
That is interesting - both psql and JDBC merely submit statements for
the backend to process, so generally you would expect no difference in
execution plan or performance.
It might be worth setting "log_statement=true" in postgresql.conf and
checking that you are executing *exactly* the same statement in both
JDBC and psql.
regards
Mark
P.s : lets see the output from EXPLAIN ANALYZE :-)
Bill Chandler wrote:
>Thanks for the advice.
>
>On further review it appears I am only getting this
>performance degradation when I run the command via
>a JDBC app. If I do the exact same query from
>psql, the performance is fine. I've tried both the
>JDBC2 and JDBC3 jars. Same results.
>
>
>
>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2004-07-09 01:41:58 | Re: Availability of a Signed Version of postgresql.jar |
| Previous Message | Dario V. Fassi | 2004-07-08 23:58:42 | Re: Availability of a Signed Version of postgresql.jar |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-07-09 01:41:50 | Re: Working on huge RAM based datasets |
| Previous Message | Bill Chandler | 2004-07-08 20:49:21 | Re: Terrible performance after deleting/recreating indexes |