Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
f3c14d85
Commit
f3c14d85
authored
Sep 09, 2019
by
Russell Dickenson
Committed by
Evan Read
Sep 09, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Standardised punctuation at end of sentences
parent
2e8cf4d5
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
doc/development/background_migrations.md
doc/development/background_migrations.md
+4
-4
No files found.
doc/development/background_migrations.md
View file @
f3c14d85
...
@@ -302,18 +302,18 @@ for more details.
...
@@ -302,18 +302,18 @@ for more details.
## Best practices
## Best practices
1.
Make sure to know how much data you're dealing with
1.
Make sure to know how much data you're dealing with
.
1.
Make sure that background migration jobs are idempotent.
1.
Make sure that background migration jobs are idempotent.
1.
Make sure that tests you write are not false positives.
1.
Make sure that tests you write are not false positives.
1.
Make sure that if the data being migrated is critical and cannot be lost, the
1.
Make sure that if the data being migrated is critical and cannot be lost, the
clean-up migration also checks the final state of the data before completing.
clean-up migration also checks the final state of the data before completing.
1.
Make sure to know how much time it'll take to run all scheduled migrations
1.
Make sure to know how much time it'll take to run all scheduled migrations
.
1.
When migrating many columns, make sure it won't generate too many
1.
When migrating many columns, make sure it won't generate too many
dead tuples in the process (you may need to directly query the number of dead tuples
dead tuples in the process (you may need to directly query the number of dead tuples
and adjust the scheduling according to this piece of data)
and adjust the scheduling according to this piece of data)
.
1.
Make sure to discuss the numbers with a database specialist, the migration may add
1.
Make sure to discuss the numbers with a database specialist, the migration may add
more pressure on DB than you expect (measure on staging,
more pressure on DB than you expect (measure on staging,
or ask someone to measure on production)
or ask someone to measure on production)
.
[
migrations-readme
]:
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/spec/migrations/README.md
[
migrations-readme
]:
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/spec/migrations/README.md
[
issue-rspec-hooks
]:
https://gitlab.com/gitlab-org/gitlab-ce/issues/35351
[
issue-rspec-hooks
]:
https://gitlab.com/gitlab-org/gitlab-ce/issues/35351
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment