Changing table wp_postmeta for better performance?

(@dailce)

Was looking at possible ways to improve performance and came across this

http://mysql.rjweb.org/doc.php/index_cookbook_mysql#speeding_up_wp_postmeta

 CREATE TABLE wp_postmeta (
        post_id BIGINT UNSIGNED NOT NULL,
        meta_key VARCHAR(255) NOT NULL,
        meta_value LONGTEXT NOT NULL,
        PRIMARY KEY(post_id, meta_key),
        INDEX(meta_key)
        ) ENGINE=InnoDB;

Anyone have experience or recommend this be done?

Viewing 2 replies - 1 through 2 (of 2 total)

Dion
(@diondesigns)

6 years, 8 months ago

While there are a couple good improvements in that table schema, please do not attempt to use it! The _postmeta table requires its meta_id column, and removing it will break WordPress.

Which is unfortunate, because a (post_id, meta_key) unique index eliminates the need for the column. There’s a lot of “that’s the way it’s always been done” code in WordPress, and this is an example of “it’s time to do things differently”.

Using InnoDB as the storage engine is also a good idea. However, please note that the post_id column requires its own BTREE index.

Thread Starter dailce
(@dailce)

6 years, 8 months ago

Guess I’ll leave it alone then. You say “Using InnoDB as the storage engine is also a good idea. However, please note that the post_id column requires its own BTREE index.”

What do you mean? What do I need to do to accomplish this?

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Changing table wp_postmeta for better performance?’ is closed to new replies.

Changing table wp_postmeta for better performance?

Topics

Topics with no replies

Non-support topics

Resolved topics

Unresolved topics

All topics