Temporary table causing instability in innodb engine

Hi @jstidd, thanks for reaching out to us.

This was added in the most recent plugin release in order to improve the performance of the user counts calculation that drives the table at the top of the Login Security > Settings page.

There is no inherent instability in using temporary tables and the performance thereof is significantly better than using a persistent table. It’d be interesting to know the circumstances of why temporary tables cause instability in your configuration and the details around any errors/messages you see when they’re used.

If you’d still prefer temporary tables to be bypassed, you can adjust the permissions for the WordPress database user to not have the ability to create temporary tables. Once that’s done, the plugin will automatically create a persistent table instead, although we’d strongly advise against this in favour of attempting to resolve the issues with temporary tables that you’re seeing.

Thanks,
Peter.

Hi Peter,

We encountered the same as well. We’re using MySQL innoDB cluster and it only supports innoDB engine. Backing up the cluster failed due to this table using memory storage engine. The bigger concern for us is that we’re in the midst of bulk purchasing Wordfence for all our sites. Can you provide a more robust workaround for this?

Hi @uberjoejitsu, thanks for reaching out.

We do normally require a separate topic for each user in case the solutions (even to similar problems) are different to prevent them becoming confusing. However, in this case as I’m unable to discuss the Premium version of Wordfence or guarantee product changes, I would contact presales @ wordfence . com highlighting your use-case and the temporary tables issue to see if we can find an appropriate resolution.

Thanks,
Peter.