Skip to content

45354 Adds composite index to postmeta table#10987

Open
nimesh-xecurify wants to merge 2 commits intoWordPress:trunkfrom
nimesh-xecurify:45354-postmeta-index
Open

45354 Adds composite index to postmeta table#10987
nimesh-xecurify wants to merge 2 commits intoWordPress:trunkfrom
nimesh-xecurify:45354-postmeta-index

Conversation

@nimesh-xecurify
Copy link

Improves performance for common meta queries by introducing a composite index on meta_key and post_id in the postmeta table.

Ensures the index is added during new installations via the schema definition and through an upgrade routine for existing sites. Includes new tests to verify the schema update and the upgrade path.

Trac ticket: https://core.trac.wordpress.org/ticket/45354

Use of AI Tools

Improves performance for common meta queries by introducing a composite index on `meta_key` and `post_id` in the `postmeta` table.

Ensures the index is added during new installations via the schema definition and through an upgrade routine for existing sites. Includes new tests to verify the schema update and the upgrade path.
@github-actions
Copy link

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props nimeshatxecurify.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions
Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant