2 個答案
- 最新
- 最多得票
- 最多評論
2
Hi! Thanks for the question and posting the details of you research. Seems this indeed is a defect in the configuration system. We are researching it with the goal of having it fixed in the next RDS for MariaDB 10.4 series release.
Meanwhile, we tested that the following workarounds can successfully turn off the rowid_filter, which you can use before a fix is available:
Either ONE of the following would work. Note: 1st approach only needs to be done once, while the 2nd approach affects only the current session and needs to repeat for every time a session starts.
1. Set the ‘init_connect’ in parameter group to SET optimizer_switch="rowid_filter=off"
mysql> show variables like 'init_connect';
+---------------+-----------------------------------------+
| Variable_name | Value |
+---------------+-----------------------------------------+
| init_connect | SET optimizer_switch="rowid_filter=off" |
+---------------+-----------------------------------------+
2. Alternatively, after logging into a session, set the session optimizer_switch parameter with rowid_filter=off.
mysql> set @@session.optimizer_switch="rowid_filter=off";
已回答 2 年前
0
Any further update if it had been fixed? I understand "workaround", but it only changes the setting for the current session, which i can not control through the application.
已回答 2 年前
相關內容
- 已提問 1 年前
- AWS 官方已更新 2 年前