password_policy makes use of the mysql TEXT column type on the 'path' database column. Because of this, database lookups that include the sections_data table are unable to use MySQL's in memory temporary tables due to the inclusion of a TEXT field, and so temporary tables must be created on disk for each of these lookups. This results in a considerable performance issue as on-disk temporary tables can have a massive effect on performance. I don't see any need for this column to be of type TEXT. Wouldn't a varchar(255) suffice?

Comments

hass’s picture

hass commented
Status: Active » Closed (works as designed)

I'm sorry, but varchar(255) may not suffice here. The field use TEXT for paths as blocks also does. We cannot guess how many paths someone will add to these textarea and 255 chars is really not enough. The module need to follow the block visibility logic, but if blocks change we can follow blocks.

How about blocks and the issue you described?