Dan Buettner wrote:
SHOW PROCESSLIST should show local queries as well as remote - in my
experience, it has been utterly reliable in terms of showing all
current queries, regardless of origin.
InnoDB by default uses a single "tablespace", which some people do
find inefficient because it never ge
SHOW PROCESSLIST should show local queries as well as remote - in my
experience, it has been utterly reliable in terms of showing all
current queries, regardless of origin.
InnoDB by default uses a single "tablespace", which some people do
find inefficient because it never gets smaller even after
Dan Buettner wrote:
Michael -
You should see all running queries in the output of SHOW PROCESSLIST.
MyISAM is a multiple-reader/single-writer design, also known as table
locking design - that is to say, you can have lots of threads reading
simultaneously, but only one writing. Also, when one i
Michael -
You should see all running queries in the output of SHOW PROCESSLIST.
MyISAM is a multiple-reader/single-writer design, also known as table
locking design - that is to say, you can have lots of threads reading
simultaneously, but only one writing. Also, when one is writing,
reading th
I have a large database, about a million records in some tables, and I
am trying to troubleshoot some stalls in our application. We have
assumed that slow query speed causes the stalls, however, when my web
app stalls I do not see the query in process list. What we see is the
web page stall
