Add support for partial indexes and concurrent indexes in postgres #793
369
−114
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
LordSimal
approved these changes
Dec 26, 2024
markstory
force-pushed
the
index-improvements
branch
from
d116b1c to
d65b163
Compare
concurrent indexes are critical to supporting zero downtime migration workflows with postgres.
implement partial indexes in postgres, sqlite and sqlserver
markstory
force-pushed
the
index-improvements
branch
from
d65b163 to
d493407
Compare
markstory
force-pushed
the
index-improvements
branch
from
d493407 to
520bba1
Compare
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.
Add support for
CREATE INDEX CONCURRENTLYin postgres. This is an important feature for deploying indexes without downtime. I've also added support for partial indexes viaCREATE INDEX ... WHEREwhich is supported in postgres, sqlserver and sqlite. I've only implemented SQL fragment support forWHEREclauses on indexes as supportingQueryExpressionobjects was complicated because cakephp/database doesn't expose good APIs for compiling expressions into SQL fragments with parameters inserted.