complicated.
Try to find out what software issued that SQL statement and its intended target.
- Original Message -
From: Connie A. Logg [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Wednesday, November 15, 2006 11:18:31 PM GMT-0500 US/Eastern
Subject: More info about 40001 SQL_NO_CACHE
16, 2006 8:41 AM
To: Logg, Connie A.
Subject: RE: More info about 40001 SQL_NO_CACHE
Looks like this may have been fixed in 5.0.25 or above, so if it's the same
bug, you're good to go.
http://bugs.mysql.com/bug.php?id=21288
Howard
-Original Message-
From: Logg, Connie A. [mailto
This showed up in 'show processlist' and it had had an active time of about 4
days. Numerous other inquiries were hung behind it, although the other
inquiries completed eventually...but they were so slow as to backup the data
base entry code and extraditions for the analysis by several hours.
