• We’re seeing lots of table locking when the plugin is attempting to prune the logs from the DB. Changing the DB engine to INNODB helps with this. However, we see that the tables are set to MyISAM by default and force-ably converts existing tables to this on upgrade. If there’s some reason we’re missing, could this be changed to INNODB by default, if supported, or at least not alter existing tables to a different engine?

Viewing 1 replies (of 1 total)
  • Plugin Contributor Adam Salah

    (@adam1318)

    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,

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.