Here at Percona, we operate on the premise that full transparency makes a product better. We strive to build the best open-source database products, but also to help you manage any issues that arise in any of the databases that we support. And, in true open source form, report back on any issues or bugs you might encounter along the way.
We constantly update our bug reports and monitor other boards to ensure we have the latest information, but we wanted to make it a little easier for you to keep track of the most critical ones. These posts are a central place to get information on the most noteworthy open and recently resolved bugs.
In this September 2022 edition of our monthly bug report, we have the following list of bugs:
Percona Server for MySQL/MySQL Bugs
PS-8328(MySQL#108316): Some queries with “group_concat” and “Group by with rollup” can either crash the server or return very unexpected wrong results.
It is happening with 8.0 whereas 5.7 is not repeating this behavior.
Reported Affected Version/s: 8.0.28, 8.0.29, 8.0.30
MySQL#96071: According to performance schema the new TempTable engine uses about three times as much memory as MEMORY for the internal TempTable created by Query 10 of DBT3.
Q10:
mysql> select c_custkey, c_name, sum(l_extendedprice * (1 - l_discount)) as revenue, c_acctbal, n_name, c_address, c_phone, c_comment from customer, orders, lineitem, nation where c_custkey = o_custkey and l_orderkey = o_orderkey and o_orderdate >= '1993-11-01' and o_orderdate < date_add( '1993-11-01' ,interval '3' month) and l_returnflag = 'R' and c_nationkey = n_nationkey group by c_custkey, c_name, c_acctbal, c_phone, n_name, c_address, c_comment order by revenue desc LIMIT 20;
MySQL 8.0 has introduced TempTable as the new, default internal temporary table storage engine to speed up query processing.
Please note that this behavior is not repeating in MySQL 8.0.29
Reported Affected Version/s: 8.0.16
PS-8327: ALTER TABLE … CHECK PARTITION inside procedure causes server to Aborted connection and Got an error writing communication packets in 5.7 where in 8.0 we encountered with Trying to reconnect.
Reported Affected Version/s: 5.7.38, 8.0.28
ZFS Bug:
Failure reported when InnoDB cluster in Multi-Primary mode used and it upgraded to 8.0.30 from 8.0.29 and restarted one of the nodes after it successfully joined the cluster after upgrade and then it failed to start with error “The redo log file ./#innodb_redo/#ib_redo1 size 647168 is not a multiple of innodb_page_size”
So the issue is with the FALLOC_FL_ZERO_RANGE flag where documentation says that not all filesystems support it and an error should be returned if it’s not supported. However, with ZFS no error is returned so if FALLOC_FL_ZERO_RANGE is replaced with 0 in f.cpp then the file is created properly.
fallocate() fails on ZFS when used with FALLOC_FL_ZERO_RANGE and it doesn’t even return the error, so it’s a problem in kernel/glibc/driver, not from the MySQL end.
So fallocate implementation is broken in the sense of returning 0 (success) even though it has not changed the (uncompressed) size of the file (which your experiments with f.cpp), then indeed using glibc2.12 variant of MySQL could have saved you from experiencing this bug, while using glibc2.17 variant (which is built on machine which supports FALLOC_FL_ZERO_RANGE) has exposed you to the problem.
For a workaround and detailed explanation of this issue, please refer https://bugs.mysql.com/bug.php?id=108012
Reported Affected Version/s: 8.0.30
Please note that this is a ZFS bug, not a MySQL bug and users need to study workarounds.
Percona XtraDB Cluster
PXC-4012: Node leaves Percona XtraDB Cluster while running concurrent CREATE USER IF NOT EXISTS when using password_history option.
Reported Affected Version/s: 8.0.28
PXC-3944: DDLs replicated as Total Order Isolation (TOI) fails constantly with Deadlock found when trying to get lock; try restarting transaction error after setting repl.max_ws_size. However, the problem is not seen after setting wsrep_max_ws_size` (maximum write-set size) from a different session.
Reported Affected Version/s: 8.0.27
Percona Toolkit
PT-2072: pt-duplicate-key-checker chokes on columns that contain a line-break
Reported Affected Version/s: 3.4.0
PT-2066: While running pt-online-schema-change where MySQL instance is in AWS RDS and MySQL is connected to a non-default port is raising the error saying.
Cannot connect to MySQL: DBI connect(‘my_db;host=[db instance].rds.amazonaws.com;mysql_read_default_group=client’,’admin’,…) failed: Can’t connect to MySQL server on ‘[db instance].rds.amazonaws.com:3306’ (110) at /usr/bin/pt-online-schema-change line 2345.
As a workaround to this problem, we can pass the connection options via DSN.
Please note that it is a private bug that won’t be available publicly.
Reported Affected Version/s: 3.3.1
Percona Monitoring and Management (PMM)
PMM-10075: When there is at least one service added to PMM and we changed the password where password contains quotes say “admin123” then re-login is failed saying invalid user or password.
Reported Affected Version/s: 2.28.0
PMM-10454: By going “share” over a panel’s title on any dashboard and clicking on the ‘Direct link rendered image’ logged error “Failed to load resource: the server responded with a status of 404 (Not Found)” and dashboard image has 404 error message along with Welcome panel.
Reported Affected Version/s: 2.29.0
PMM-10364: After upgraded percona-pg_stat_monitor version to 1.0.1, and after that pmm-agent raised the errors getNewBuckets failed: failed to query pg_stat_monitor: pq: pg_stat_monitor: incorrect number of output arguments…
Reported Affected Version/s: 2.28.0
Percona XtraBackup
PXB-2797: When importing a single table (IMPORT TABLESPACE) from a backup made using XtraBackup and the table contains a full-text index the import process failed with ERROR 1808 (HY000) at line 132: Schema mismatch (Index x field y is ascending which does not match metadata file which is descending).
Reported Affected Version/s: 8.0.28
Summary
We welcome community input and feedback on all our products. If you find a bug or would like to suggest an improvement or a feature, learn how in our post, How to Report Bugs, Improvements, and New Feature Requests for Percona Products.
For the most up-to-date information, be sure to follow us on Twitter, LinkedIn, and Facebook.
Quick References:
Report a Bug in a Percona Product
___
About Percona:
As the only provider of distributions for all three of the most popular open source databases—PostgreSQL, MySQL, and MongoDB—Percona provides expertise, software, support, and services no matter the technology.
Whether it’s enabling developers or DBAs to realize value faster with tools, advice, and guidance, or making sure applications can scale and handle peak loads, Percona is here to help.
Percona is committed to being open source and preventing vendor lock-in. Percona contributes all changes to the upstream community for possible inclusion in future product releases.
