refactor(db/build): drop source index, add event index #1228
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.
source
column was used by legacy deployment implementation so should be dropped. it also had high cardinality, so is likely relatively large on bigger installations.event
has become more of a bottleneck for some queries for very busy repos when querying builds by event. we recommend adding it.the changes in this PR only affect new installations. to accommodate these in existing installations, drop the
source
index (concurrently on Postgres) and add the new one withCREATE INDEX CONCURRENTLY IF NOT EXISTS builds_event ON builds (event);
(for Postgres).probably still wise to create the index prior to upgrading unless you have the
VELA_DATABASE_SKIP_CREATION
orDATABASE_SKIP_CREATION
flag set to true, since the default statements don't useCONCURRENTLY
on Postgres.