Hello,@supersoju
Thank you for contacting support and we’re happy to assist you.We will investigate this further and keep you updated with any progress.
Your patience is much appreciated.
Thank you for your understanding!
Best wishes,
Hello, @supersoju,
Thank you for your patience.
Could you kindly provide the exact version where you encountered the issue? This will help us assist you better, as we haven’t received similar concerns from our other clients.
Thank you, and have a great day!
Best regards,
Hello,
It’s in the current version 9.12. Not sure what can be done as far as the table locking goes apart from switching from MyISAM. We had the cleanup setting at 30 days, and when it started it’s process it was working on over 100k DB rows which locked everything up. We’ve since adjusted it to 7 days, but that will still be 10s of thousands of rows. We truncated the table and converted the tables to InnoDB. We want to make sure this change isn’t undone during the next update.
The exact area is in the WPSR_install() function in the seo-redirection.php file.
For example, this is the first item on line 1182:
//check if Innodb convert it to myisam.
$status = $wpdb->get_row(“SHOW TABLE STATUS WHERE Name = ‘$table_name'”);
if ($status->Engine == ‘InnoDB’) {
$wpdb->query(“alter table $table_name engine = MyISAM;”);
}
Hello, @supersoju,
Thank you for contacting our support team. We’re glad to assist you.
We sincerely apologize for any inconvenience this issue has caused. Rest assured, we will investigate the matter thoroughly and keep you updated with any progress.
Thank you for your patience, and have a wonderful day!
Best regards,
