So, if I understand correctly. I am not doing anything wrong in terms of the
SQL coding, it is just the speed of the postmaster right now.
I am new to PostgreSQL and SQL for that matter, but another question I have
would be:
Would indexes help at all? <-- If so, what should I index to get the best
speed?
Thanks
Gregg Berkholtz
Bruce Momjian wrote:
> > I have a few SQL query's that are taking in the range of 30-60 seconds
> > to complete. They are searching tables that are no larger than 120 rows
> > with I believe 7 columns of data each.
> > Any ideas?
> > The SQL statement is below:
> >
> > SELECT tblClientInfo.fName, tblClientInfo.lName, tblClientInfo.phoneNum,
> > tblClientLocation.locationName, tblTroubTick.TroubTickLastUpdate,
> > tblTroubTick.hoursInvested, tblSupportPersInfo.fName,
> > tblSupportPersInfo.lName, tblPriority.priority, tblTroubTick.assetID,
> > tblTroubTickStatus.troubTickStatus, tblTroubTickProblem.troubTickProblem
> >
> > FROM tblClientInfo, tblTroubTick, tblClientLocation, tblSupportPersInfo,
> > tblPriority, tblTroubTickStatus, tblTroubTickProblem
> > WHERE tblTroubTick.troubTickStatusID <> 7 AND
> > tblClientLocation.locationID = tblClientInfo.locationID AND
> > tblTroubTick.clientID = tblClientInfo.clientID AND
> > tblTroubTick.supportPersID = tblSupportPersInfo.supportPersID AND
> > tblTroubTick.priorityID = tblPriority.priorityID AND
> > tblTroubTick.troubTickStatusID = tblTroubTickStatus.troubTickStatusID
> > AND tblTroubTick.troubTickProblemID =
> > tblTroubTickProblem.troubTickProblemID;
>
> 6.5 will have a majorly improved optimizer. We hope to start beta in a
> month. Hope you can wait.
>
> --
> Bruce Momjian | http://www.op.net/~candle
> maillist@candle.pha.pa.us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
