Skip to content

question: benefits of using gh-ost for building expensive indexes? #1528

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
donhcd opened this issue Apr 7, 2025 · 0 comments
Open

question: benefits of using gh-ost for building expensive indexes? #1528

donhcd opened this issue Apr 7, 2025 · 0 comments

Comments

@donhcd
Copy link

donhcd commented Apr 7, 2025

hello! I've been playing with gh-ost lately for various reasons and I wanted to check whether it makes sense to use gh-ost to build expensive indexes. Most of what I see is related to schema changes, and I haven't yet found anything about how/whether it helps with building indexes.

Specifically, I'm hoping that setting the chunk-size will allow us to throttle the operations we need to run for the index build at any time. Is this something that will work for index builds? If so, it could be a safer way to run big index builds, even if it has the higher total cost of copying my table first and replicating it

thanks for your help!

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

No branches or pull requests

1 participant