Details
Description
Not sure if it counts as a bug since system tables are not supposed to be altered by users. Split from MDEV-35557 for tracking / documentation purposes at least:
CREATE SERVER s1 FOREIGN DATA WRAPPER mysql OPTIONS (HOST '127.0.0.1'); |
ALTER TABLE mysql.servers ENGINE=innodb; |
FLUSH PRIVILEGES; |
drop server s1; |
results in
temp.mdev_35557 [ fail ]
|
Test ended at 2024-12-13 16:28:12
|
|
CURRENT_TEST: temp.mdev_35557
|
mysqltest: At line 22: query 'drop server s1' failed: 1477: The foreign server name you are trying to reference does not exist. Data source error: s1
|
Attachments
Issue Links
- split from
-
MDEV-35557 SIGSEGV in get_server_from_table_to_cache | servers_load, UBSAN null pointer passed as argument 1, which is declared to never be null
-
- Closed
-
see marko's analysis at https://jira.mariadb.org/browse/MDEV-35557?focusedCommentId=295928&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-295928
Bringing the call to table->use_all_columns() forward seems to fix the testcase:
0efc45e922e upstream/bb-10.5-mdev-35641 MDEV-35641 bring call to use_all_columns() forward when reading from mysql.servers