Postgres Pro
Downloads
Home   >   mailing lists

Thread: SQL query _slow_

SQL query _slow_

From
Gregg Berkholtz
Date:
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;

Thanks for any help!
Gregg Berkholtz

Re: [SQL] SQL query _slow_

From
Bruce Momjian
Date:
> 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

Re: [SQL] SQL query _slow_

From
Gregg Berkholtz
Date:
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

Re: [SQL] SQL query _slow_

From
Bruce Momjian
Date:
> 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?

Not sure.  If EXPLAIN is slow showing results, it is just the optimizer.

--
  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

Re: [SQL] SQL query _slow_

From
Gregg Berkholtz
Date:
EXPLAIN -- What is that?

Bruce Momjian wrote:

> > 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?
>
> Not sure.  If EXPLAIN is slow showing results, it is just the optimizer.
>
> --
>   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

--
-----------------------------------------------------
/////////////        Gregg Berkholtz - Owner
|    G B    | Computer consulting, sales and support
| Computers |
\\\\\\\\\\\\\       INFO: www.gbcomputers.com

Re: [SQL] SQL query _slow_

From
Bruce Momjian
Date:
> EXPLAIN -- What is that?

A psql command.

>
> Bruce Momjian wrote:
>
> > > 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?
> >
> > Not sure.  If EXPLAIN is slow showing results, it is just the optimizer.
> >
> > --
> >   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
>
> --
> -----------------------------------------------------
> /////////////        Gregg Berkholtz - Owner
> |    G B    | Computer consulting, sales and support
> | Computers |
> \\\\\\\\\\\\\       INFO: www.gbcomputers.com
>
>
>


--
  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