Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
c45fa559
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,发现更多精彩内容 >>
提交
c45fa559
编写于
3月 20, 2007
作者:
B
Bruce Momjian
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
In FAQ, reference upgrade info via URL.
上级
d89b9683
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
6 addition
and
64 deletion
+6
-64
doc/FAQ
doc/FAQ
+2
-32
doc/src/FAQ/FAQ.html
doc/src/FAQ/FAQ.html
+4
-32
未找到文件。
doc/FAQ
浏览文件 @
c45fa559
Frequently Asked Questions (FAQ) for PostgreSQL
Last updated:
Fri Feb 23 14:06:15 ES
T 2007
Last updated:
Tue Mar 20 13:43:40 ED
T 2007
Current maintainer: Bruce Momjian (bruce@momjian.us)
...
...
@@ -430,37 +430,7 @@
3.6) What is the upgrade process for PostgreSQL?
PostgreSQL major releases include new features and occur roughly once
every year. A major release is numbered by increasing either the first
or second part of the version number, e.g. 8.1 to 8.2.
Major releases usually change the internal format of system tables and
data files. These changes are often complex, so we don't maintain
backward compatibility for data files. A dump/reload of the database
is required for major upgrades.
Minor releases are numbered by increasing the third part of the
version number, e.g. 8.1.5 to 8.1.6. The PostgreSQL team only adds bug
fixes to minor releases. All users should upgrade to the most recent
minor release as soon as possible. While upgrades always have some
risk, PostgreSQL minor releases fix only frequently-encountered,
security, and data corruption bugs to reduce the risk of upgrading.
The community considers not upgrading riskier than upgrading.
`
Upgrading to a minor release does not does not require a dump and
restore; merely stop the database server, install the updated
binaries, and restart the server.
3.7) What computer hardware should I use?
Because PC hardware is mostly compatible, people tend to believe that
all PC hardware is of equal quality. It is not. ECC RAM, SCSI, and
quality motherboards are more reliable and have better performance
than less expensive hardware. PostgreSQL will run on almost any
hardware, but if reliability and performance are important it is wise
to research your hardware options thoroughly. Our email lists can be
used to discuss hardware options and tradeoffs.
See http://www.postgresql.org/support/versioning.
_________________________________________________________________
Operational Questions
...
...
doc/src/FAQ/FAQ.html
浏览文件 @
c45fa559
...
...
@@ -10,7 +10,7 @@
alink=
"#0000ff"
>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<P>
Last updated:
Fri Feb 23 14:06:15 ES
T 2007
</P>
<P>
Last updated:
Tue Mar 20 13:43:40 ED
T 2007
</P>
<P>
Current maintainer: Bruce Momjian (
<A
href=
"mailto:bruce@momjian.us"
>
bruce@momjian.us
</A>
)
...
...
@@ -584,37 +584,9 @@
<H3
id=
"item3.6"
>
3.6) What is the upgrade process for PostgreSQL?
</H3>
<P>
PostgreSQL major releases include new features and occur roughly
once every year. A major release is numbered by increasing either
the first or second part of the version number, e.g. 8.1 to 8.2.
<P>
Major releases usually change the internal format of system tables
and data files. These changes are often complex, so we don't maintain
backward compatibility for data files. A dump/reload of the database
is required for major upgrades.
</P>
<P>
Minor releases are numbered by increasing the third part of the
version number, e.g. 8.1.5 to 8.1.6. The PostgreSQL team only adds
bug fixes to minor releases. All users should upgrade to the most
recent minor release as soon as possible. While upgrades always have
some risk, PostgreSQL minor releases fix only frequently-encountered,
security, and data corruption bugs to reduce the risk of upgrading.
The community considers
<i>
not
</i>
upgrading riskier than
upgrading.
</P>
`
<P>
Upgrading to a minor release does not does not require a dump and
restore; merely stop the database server, install the updated binaries,
and restart the server.
</P>
<H3
id=
"item3.7"
>
3.7) What computer hardware should I use?
</H3>
<P>
Because PC hardware is mostly compatible, people tend to believe that
all PC hardware is of equal quality. It is not. ECC RAM, SCSI, and
quality motherboards are more reliable and have better performance than
less expensive hardware. PostgreSQL will run on almost any hardware,
but if reliability and performance are important it is wise to
research your hardware options thoroughly. Our email lists can be used
to discuss hardware options and tradeoffs.
</P>
<P>
See
<a
href=
"http://www.postgresql.org/support/versioning"
>
http://www.postgresql.org/support/versioning
</a>
.
</P>
<HR>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录