Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
0451c09f
G
Gpdb
项目概览
Greenplum
/
Gpdb
通知
7
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
Gpdb
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
0451c09f
编写于
1月 14, 2002
作者:
B
Bruce Momjian
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Doc improvements.
上级
15ca0a50
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
10 addition
and
10 deletion
+10
-10
contrib/pg_upgrade/pg_upgrade.man
contrib/pg_upgrade/pg_upgrade.man
+10
-10
未找到文件。
contrib/pg_upgrade/pg_upgrade.man
浏览文件 @
0451c09f
...
...
@@ -19,10 +19,10 @@ version must be used.
1) Back up your existing data directory, preferably by making a complete
dump with pg_dumpall.
.LP
2) Copy the program
pgsql/contrib/pg_upgrade/pg_upgrade
from the current
PostgreSQL distribution
into somewhere in
your path.
2) Copy the program
\fIpgsql/contrib/pg_upgrade/pg_upgrade\fP
from the current
PostgreSQL distribution
somewhere into
your path.
.LP
3) Change your working directory to the
pgsql main directory, and type:
3) Change your working directory to the pgsql main directory, and type:
.LP
.B $ pg_upgrade -1
.sp
...
...
@@ -40,18 +40,18 @@ to install the new binaries.
.br
.B $ make install
.sp
to install the
pg_resetxlog
utility which is needed by
to install the
\fIpg_resetxlog\fP
utility which is needed by
pg_upgrade.
.LP
6) Run initdb to create a new template1 database containing the system
tables for the new release. Make sure you use settings similar to those
used in your previous version.
.LP
7) Start the new
postmaster.
(Note: it is critical that no users connect
7) Start the new
\fIpostmaster.\fP
(Note: it is critical that no users connect
to the server until the upgrade is complete. You may wish to start the
postmaster without -i
and/
or alter pg_hba.conf temporarily.)
postmaster without -i or alter pg_hba.conf temporarily.)
.LP
8) Change your working directory to the
pgsql main directory, and type:
8) Change your working directory to the pgsql main directory, and type:
.LP
.B $ pg_upgrade -2
.sp
...
...
@@ -61,15 +61,15 @@ but with no data. It will then physically move the data files
containing non-system tables and indexes into the proper
subdirectories.
.LP
9) Restore your old
pg_hba.conf
if needed to allow user logins.
9) Restore your old
\fIpg_hba.conf\fP
if needed to allow user logins.
.sp
.LP
10) Carefully examine the contents of the upgraded databases. If you
detect problems, you'll need to recover by restoring from your full
pg_dump backup. You can delete the
pg_upgrade_info/
directory when you
pg_dump backup. You can delete the
\fIpg_upgrade_info/\fP
directory when you
are satisfied.
.LP
The upgraded databases will be in an un-vacuumed state. You will
probably want to run a
VACUUM ANALYZE
before beginning production work.
probably want to run a
\fIVACUUM ANALYZE\fB
before beginning production work.
.SH SEE ALSO
initdb(1), postmaster(1), pg_dump(1), pg_dumpall(1), vacuumdb(1)
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录