-
Notifications
You must be signed in to change notification settings - Fork 103
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
[master] < MG-parallelize-index-creation #882
Conversation
In the RecoverIndicesAndConstraints function it is now possible to execute the index recration after a crash in a multithreaded fashion.
The issue was caused by the difference when trying to recover from snapshots and WAL files. The parallelized version of index creation is based on RecoveryInfo::vertex_batches which is always empty in the case of recovering from WAL files. In that case the sequential index creation will be used.
Co-authored-by: János Benjamin Antal <antaljanosbenjamin@users.noreply.github.com>
@gvolfing I think this should be disabled by default (an opinion). Another thing, I think the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we add tests here to check parallel index creation?
|
… during parallel index creation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
7dec982
to
64fd281
Compare
@antoniofilipovic & @gvolfing I have a release note in the docs PR, but the PR is still a draft, so is there more info coming? Seems like the index page should be updated as well Maybe this has nothing to do with creating indexes outside of the recovery process? Can I use this for regular index creation? |
[master < MG-parallelize-index-creation] PR