Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
2be54f1b
G
gitlab-foss
项目概览
李少辉-开发者
/
gitlab-foss
通知
15
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
gitlab-foss
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
2be54f1b
编写于
7月 11, 2018
作者:
M
Mark Chao
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Fix doc for large table column rename
上级
c2a0a3ab
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
2 addition
and
2 deletion
+2
-2
doc/development/what_requires_downtime.md
doc/development/what_requires_downtime.md
+2
-2
未找到文件。
doc/development/what_requires_downtime.md
浏览文件 @
2be54f1b
...
...
@@ -198,14 +198,14 @@ And that's it, we're done!
## Changing The Schema For Large Tables
While
`change_column_type_concurrently`
and
`rename_column_concurrently`
can be
used for changing the schema of a table without downtime it doesn't work very
used for changing the schema of a table without downtime
,
it doesn't work very
well for large tables. Because all of the work happens in sequence the migration
can take a very long time to complete, preventing a deployment from proceeding.
They can also produce a lot of pressure on the database due to it rapidly
updating many rows in sequence.
To reduce database pressure you should instead use
`change_column_type_using_background_migration`
or
`rename_column_
concurrently
`
`change_column_type_using_background_migration`
or
`rename_column_
using_background_migration
`
when migrating a column in a large table (e.g.
`issues`
). These methods work
similarly to the concurrent counterparts but uses background migration to spread
the work / load over a longer time period, without slowing down deployments.
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录