[rt-users] Odd Question

[Mat]

from the look of it, what someone has done, is searched for a ticket with 2
or more differenet requestors.
The query just to find tickets by 1 requestor is very heavy (and shouldn't
really be! hopefully this will be fixed up in the future), adding more
requestors onto it blows the query right out.

I've actually changed around my search pages so staff cannot search via
requestor (they need to go through our customer info pages to get the
tickets).

I wouild suggest making it so only one requestor can be in the search query
at a time, then you will see this query disappear i think

  -----Original Message-----
  From: rt-users-admin at lists.fsck.com
[mailto:rt-users-admin at lists.fsck.com]On Behalf Of Derek Buttineau
  Sent: Friday, 1 February 2002 4:31 AM
  To: rt-users at lists.fsck.com
  Subject: [rt-users] Odd Question


  Been running into this lately with the our RT2-0-11 setup, and have seen
the same issue coming from previous versions back to RT2-0-1..

  We've been seeing RT overload itself on the SQL backend (mysql)
occasionally as of late.

  Today I managed to catch the query that was causing it, which is:

  SELECT DISTINCT main.* FROM Tickets main, Watchers Watchers_1, Watchers
Watchers_3, Watchers Watcher

  When this happens it locks the RT Tickets table while it copies the query
to a tmp database:

  | 5933 | rtuser   | localhost          | rt2      | Query   | 447  |
Copying to tmp table | SELECT DISTINCT main.* FROM Tickets main, Watchers
Watchers_1, Watchers Watchers_3, Watchers Watcher |

  However, we're seeing this sit for up to hours without resolution.. I end
up having to flush the processes in order for RT to resume operation.

  Has anyone else ran into this and/or know how to resolve it?

  Thanks,


  Derek

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20020201/64e91094/attachment.htm>