db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Carter" <joe.car...@excite.com>
Subject Re: Performance issues when using postgresql-8.1-404.jdbc3.jar
Date Wed, 14 Jun 2006 14:13:47 GMT
On 14/06/06, Greg Monroe <Greg.Monroe@dukece.com> wrote:
> You probably have done this, but does your Raw SQL statement
> match the one generated by Torque exactly?  Sometime statement
> syntax differences can generate different execution plans
> which causes one query to use indices and another not to.
> In my experience this is the most likely suspect for Select
> performance problems and generally can be fixed by adding
> appropriate indices.
> Yes, I took the output from p6spy and replicated that.
It's possible p6spy has reordered it, but I don't think so.
The queries are very simple selects though, so I'm pretty certain
it's not dodging indexes. These queries don't table scan for sure
as they're used on systems with multiple-millions of rows.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message