Bug #109700 Fix for #33630199 in 8.0.32 not reflected in the documentation and release notes
| Submitted: | 19 Jan 2023 10:52 | Modified: | 31 May 2023 2:51 |
|---|---|---|---|
| Reporter: | Przemyslaw Malkowski | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | 8.0.32 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | mysqldump, set-gtid-purged | ||
[19 Jan 2023 10:52]
Przemyslaw Malkowski
[19 Jan 2023 15:43]
MySQL Verification Team
Hello Przemyslaw, Thank you for the report. Thanks, Umesh
[23 Jan 2023 14:33]
Yura Sorokin
This also duplicates https://bugs.mysql.com/bug.php?id=109685 where the author claims that this may not be just a documentation bug because after the 8.0.32 patch, the generated dump will include FTWRL that will require additional privileges that were not necessary before.
[22 Feb 2023 19:20]
Philip Olson
Posted by developer: Thank you, this is an interesting situation. The related mysqldump documentation deserves attention and an update, as you described. Related, the increased privilege requirement for --single-transaction added in 8.0.32 was reduced in 8.0.33 to situations where both gtid_mode = ON (default is OFF) and --set-gtid-purged = AUTO|ON (default is AUTO).
[31 May 2023 2:51]
Philip Olson
Posted by developer: The 8.0.32 release notes were updated in February to include the following: Limitation: This fix adds a requirement for the RELOAD privilege when using --single-transaction to execute FLUSH TABLES WITH READ LOCK; the MySQL team is investigating a solution. Unfortunately this bug report wasn't closed at the time, sorry for the delay. The bug regression was fixed in 8.0.33.
[31 May 2023 3:36]
Philip Olson
Posted by developer: Note: several related documentation changes were committed today that hopefully help clarify the situation.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.047 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.