Why not all Inno_DB?

I forgot this error then too from WP warning:
Action Scheduler: 1127 past-due actions found; something may be wrong. Read documentation ?

Hi @18tommyboy, thanks for reaching out about this.

The MEMORY table seen in your screenshot is from the new more-efficient method of counting users with temporary tables. Due to the type of query being used, Wordfence tries?MEMORY?first, then?MyISAM, which is second most efficient in this case, then falls back to?InnoDB?otherwise. It does use a permanent table if temporary tables aren’t allowed on your database.

Thanks,
Peter.

I have only InnoDB like all modern databases. Can set this to search in InnoDB or swith off this “memory” tables? Very slowing down database and Plesk warn for error for this table.

Hi @18tommyboy,

There is a configuration option coming in a future release of our Login Security module to avoid the use of MEMORY tables if that’s your preference. I can’t comment on precise delivery dates here on the forums as workloads can change from time-to-time.

In the mean time, the plugin is designed to create a permanent table if you disable temporary tables on your database. These can then be forced to use InnoDB. The command:
alter table wp_wfls_role_counts engine=innodb;?worked for me, and it doesn’t get changed when the plugin gets updated.

Thanks again,
Peter.

Okay, I changed:

https://freeimage.host/i/HvkF7uS

but WordPress update still take forever… Can′t finish it.

Hi @18tommyboy,

The “The storage engine for the table doesn’t support check” is a normal response for MEMORY or HEAP tables, so have temporary tables been disabled – and has the plugin generated its alternative MyISAM table for this before changing the type to InnoDB?

Thanks,
Peter.

I don′t now, but the SQL command not help:
Action Scheduler: 2437 past-due actions found; something may be wrong. Read documentation ?

and still very slow sites