Merge ~cjwatson/launchpad:db-split-bpph-creator-index into launchpad:db-devel
Proposed by
Colin Watson
Status: | Merged |
---|---|
Approved by: | Colin Watson |
Approved revision: | b85c45e2fc6802d4be22ef3cadd0fc3e0eb9ab85 |
Merge reported by: | Otto Co-Pilot |
Merged at revision: | not available |
Proposed branch: | ~cjwatson/launchpad:db-split-bpph-creator-index |
Merge into: | launchpad:db-devel |
Diff against target: |
34 lines (+9/-4) 2 files modified
database/schema/patch-2210-11-1.sql (+0/-4) database/schema/patch-2210-11-2.sql (+9/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
William Grant | db | Approve | |
Review via email: mp+380770@code.launchpad.net |
Commit message
Split BPPH(creator) index into a separate DB patch
This works because the index is only needed in a few places (person
merging, team visibility changes, closing accounts, and PersonPruner in
garbo), so if it's absent for a short time while the index is created
with CONCURRENTLY then nothing goes too badly wrong.
Changing an already-committed patch shouldn't be taken as precedent. We
can get away with it in this case, but we'll need to fix things up
manually on staging.
Description of the change
On production, the index will have to be created separately with CONCURRENTLY, since BinaryPackagePu
To post a comment you must log in.
Do note in the commit message that this is highly evil and not precedent. But otherwise looks good.