RMB-587: Prepare f_unaccent indexes #654
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
julianladisch
requested review from
adamdickmeiss,
craigmcnally,
hjiebsco and
MikhailFokanov
|
Kudos, SonarCloud Quality Gate passed!
|
adamdickmeiss
approved these changes
May 12, 2020
|
I've successfully tested it with mod-inventory-storage. On a million instances it reduces the upgrade time by more than 50%. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RMB-587
Prepare new f_unaccent indexes in addition
to the existing indexes. This takes some time, but this time is saved when upgrading the module to RMB >= 29.4 (Goldenrod). Upgrade to RMB 29.3.3 to create these indexes in advance, for example at night a few days before the module upgrade to Goldenrod.
The new indexes have the _p name suffix and are updated on CRUD operations of the underlying data.
When upgrading to RMB >= 29.4 the old index is deleted and replaced by the new index, this is a fast index rename without index recreation.