Reduce the number of indexes on the node_field_* tables

'indexes' => array( 'node_changed' => array('changed'), 'node_created' => array('created'), 'node_default_langcode' => array('default_langcode'), 'node_langcode' => array('langcode'), 'node_frontpage' => array('promote', 'status', 'sticky', 'created'), 'node_status_type' => array('status', 'type', 'nid'), 'node_title_type' => array('title', array('type', 4)), 'node_type' => array(array('type', 4)), 'nid' => array('nid'), 'vid' => array('vid'), 'uid' => array('uid'), ),

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 7 months ago →
🇦🇺Australia acbramley
We need a title and IS update here about exactly what we're proposing to change.
Comment about 2 months ago →
🇺🇸United States smustgrave
Wanted to bump 1 more time.
Comment about 2 months ago →
🇬🇧United Kingdom catch
This still needs to be done I think but it's not easy.

We'd need to check all the queries that get run on these tables, then check which of the existing indexes they use if any. There might be another issue around this.
Comment about 2 months ago →
🇺🇸United States smustgrave
Would it be easier to remove 1-2 at a time?
Comment about 2 months ago →
🇬🇧United Kingdom catch
We can probably only remove one or two, the problem is knowing which ones are safe to remove.
Comment about 2 months ago →
🇺🇸United States smustgrave
There any BC policy over indexes to worry about?
Comment about 2 months ago →
🇬🇧United Kingdom catch
No, it's database schema, and less disruptive than another schema change would be.