Oracle 5.0, Справочное руководство

Страница: 756 / 3232

General Thread States
736
•
FULLTEXT initialization
The server is preparing to perform a natural-language full-text search.
•
init
This occurs before the initialization of
ALTER TABLE
,
DELETE
,
INSERT
,
SELECT
, or
UPDATE
statements. Actions taken by the server in this state include flushing the binary log, the
InnoDB
log,
and some query cache cleanup operations.
For the
end
state, the following operations could be happening:
• Removing query cache entries after data in a table is changed
• Writing an event to the binary log
• Freeing memory buffers, including for blobs
•
Killed
Someone has sent a
KILL
statement to the thread and it should abort next time it checks the kill flag.
The flag is checked in each major loop in MySQL, but in some cases it might still take a short time
for the thread to die. If the thread is locked by some other thread, the kill takes effect as soon as the
other thread releases its lock.
•
Locked
The query is locked by another query.
•
logging slow query
The thread is writing a statement to the slow-query log.
•
NULL
This state is used for the
SHOW PROCESSLIST
state.
•
login
The initial state for a connection thread until the client has been authenticated successfully.
•
Opening tables
,
Opening table
The thread is trying to open a table. This is should be very fast procedure, unless something
prevents opening. For example, an
ALTER TABLE
or a
LOCK TABLE
statement can prevent opening
a table until the statement is finished. It is also worth checking that your
table_cache
[498] value is
large enough.
•
optimizing
The server is performing initial optimizations for a query.
•
preparing
This state occurs during query optimization.
•
Purging old relay logs
The thread is removing unneeded relay log files.
•
query end
This state occurs after processing a query but before the
freeing items
state.