Bug #65157 set read_only=1|0 kills performance
| Submitted: | 30 Apr 2012 17:39 | Modified: | 3 May 2012 8:13 |
|---|---|---|---|
| Reporter: | Mark Callaghan | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server | Severity: | S5 (Performance) |
| Version: | 5.1.53 | OS: | Any |
| Assigned to: | CPU Architecture: | Any |
[30 Apr 2012 17:39]
Mark Callaghan
[3 May 2012 8:13]
Dmitry Lenev
Hello Mark! This issue has the same cause as bug #57612 "SET GLOBAL READ_ONLY=1 cannot progress when a table is locked with LOCK TABLES" and has been fixed in 5.6 tree by the same patch. Therefore I am closing this bug as duplicate.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.038 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.