Bug #80601 Manual is wrong/not clear while explaining kill flag check for ALTER TABLE
| Submitted: | 3 Mar 2016 8:57 | Modified: | 4 Apr 2016 14:35 |
|---|---|---|---|
| Reporter: | Valeriy Kravchuk | Email Updates: | |
| Status: | Won't fix | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | 5.6, 5.7 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | alter, KILL, missing manual | ||
[3 Mar 2016 8:57]
Valeriy Kravchuk
[9 Mar 2016 14:17]
MySQL Verification Team
Thank you for the bug report.
[4 Apr 2016 14:35]
Paul DuBois
I asked Dmitry L about this, who indicated that this is an implementation detail subject to change. So the manual isn't going to try to be more specific here. On the other hand, this applies for ALTER TABLE operations that make a *copy*, so I'll revise the wording to include that: ALTER TABLE operations that make a table copy check the kill flag periodically for each few copied rows read from the original table. If the kill flag was set, the statement is aborted and the temporary table is deleted.
[5 Apr 2016 14:02]
Paul DuBois
Addition to previous comment: The KILL statement returns without waiting for confirmation, but the kill flag check aborts the operation within a reasonably small amount of time. Aborting the operation to perform any necessary cleanup also takes some time.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.057 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.