MariaDB 10.6.10 Compatibility?

Thanks for letting me know of your problem.

I do a lot of testing with MariaDB 10.6 (a small instance on a VM in my case), so I’m pretty sure there’s nothing systemically incompatible that software version.

Your wp-cli error message makes it look to me like you gave the command wp index-mysql upgrade --all. That is the command that converts your tables from MyISAM to InnoDB. You can try wp index-mysql status to see the current status of high-performance keys and tables.

And you can always say wp index-mysql enable --all --dry-run to see the actual Data Definition Language statements to do the enabling. Same for disable.

Please give the command wp index-mysql upload_metadata and let me know the randomized upload id. That way I can take a closer look.

I realised that I shared an instruction that can be disputed, after I posted my initial message. But here is the full monty.

dimitrisv@dvwd:/var/www/omega$ wp index-mysql disable --all --dry-run 

PHP Warning:  Module 'newrelic' already loaded in Unknown on line 0

objectcache.critical: Failed to locate and load object cache API

-- Index WP MySQL For Speed 1.4.11

-- Versions  Plugin:1.4.11 MySQL:10.6.10-MariaDB-1:10.6.10+maria~ubu2204 WordPress:6.0.2 WordPress database:53496 php:7.4.32

-- Generated from Sigma Lab Site (https://omega) at 12 Οκτωβρ?ου, 2022 13:45.

-- Do not save these statements for later use. Instead, regnerate them.

-- Dry run SQL statements. These statements were NOT run.

SET @@sql_mode := REPLACE(@@sql_mode, 'NO_ZERO_DATE', '');

ALTER TABLE wp_commentmeta DROP PRIMARY KEY, ADD PRIMARY KEY (meta_id), DROP KEY comment_id, ADD KEY comment_id (comment_id), ADD KEY meta_key (meta_key(191)), DROP KEY meta_id, DROP KEY meta_value;

ALTER TABLE wp_comments DROP PRIMARY KEY, ADD PRIMARY KEY (comment_ID), ADD KEY comment_post_ID (comment_post_ID), DROP KEY comment_approved_date_gmt, ADD KEY comment_approved_date_gmt (comment_approved, comment_date_gmt), DROP KEY comment_date_gmt, ADD KEY comment_date_gmt (comment_date_gmt), DROP KEY comment_parent, ADD KEY comment_parent (comment_parent), DROP KEY comment_author_email, ADD KEY comment_author_email (comment_author_email(10)), DROP KEY comment_ID, DROP KEY comment_post_parent_approved;

ALTER TABLE wp_options DROP PRIMARY KEY, ADD PRIMARY KEY (option_id), ADD UNIQUE KEY option_name (option_name), DROP KEY option_id;

ALTER TABLE wp_postmeta DROP PRIMARY KEY, ADD PRIMARY KEY (meta_id), ADD KEY post_id (post_id), DROP KEY meta_key, ADD KEY meta_key (meta_key(191)), DROP KEY meta_id, DROP KEY meta_value;

ALTER TABLE wp_posts DROP KEY post_name, ADD KEY post_name (post_name(191)), DROP KEY post_parent, ADD KEY post_parent (post_parent), DROP KEY type_status_date, ADD KEY type_status_date (post_type, post_status, post_date, ID), DROP KEY post_author, ADD KEY post_author (post_author);

ALTER TABLE wp_termmeta DROP PRIMARY KEY, ADD PRIMARY KEY (meta_id), ADD KEY term_id (term_id), DROP KEY meta_key, ADD KEY meta_key (meta_key(191)), DROP KEY meta_id, DROP KEY meta_value;

ALTER TABLE wp_usermeta DROP PRIMARY KEY, ADD PRIMARY KEY (umeta_id), ADD KEY user_id (user_id), DROP KEY meta_key, ADD KEY meta_key (meta_key(191)), DROP KEY umeta_id, DROP KEY meta_value;

ALTER TABLE wp_users DROP KEY display_name;

dimitrisv@dvwd:/var/www/omega$ wp index-mysql enable --all --dry-run 

PHP Warning:  Module 'newrelic' already loaded in Unknown on line 0

objectcache.critical: Failed to locate and load object cache API

-- Index WP MySQL For Speed 1.4.11

-- Versions  Plugin:1.4.11 MySQL:10.6.10-MariaDB-1:10.6.10+maria~ubu2204 WordPress:6.0.2 WordPress database:53496 php:7.4.32

-- Generated from Sigma Lab Site (https://omega) at 12 Οκτωβρ?ου, 2022 13:45.

-- Do not save these statements for later use. Instead, regnerate them.

-- Dry run SQL statements. These statements were NOT run.

SET @@sql_mode := REPLACE(@@sql_mode, 'NO_ZERO_DATE', '');

Error: -- No tables are eligible to enable.

dimitrisv@dvwd:/var/www/omega$

From this output I can see that you have already added the high-performance keys to your table.

I also spot some trouble with your object cache in this message. There is not enough information here for me to know exactly what is wrong.

objectcache.critical: Failed to locate and load object cache API

Do you use a persistent object cache on your development site? A persistent object cache makes an enormous difference to performance. If it’s not available on your hosting service, that can hurt. Many “budget” hosting providers don’t offer them.

No, that was “inherited” from my backup at Linode (Cloudways).

I removed the mu-plugin and have disabled it from my wp-config. However I am -somehow- getting this error due to New Relic!

The issue had to do with the NO_ZERO_IN_DATE,NO_ZERO_DATE sql_mode settings.

I haven’t heard back in a month whether you need more help. If you do please start a new thread.