Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
d8c21181
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,发现更多精彩内容 >>
提交
d8c21181
编写于
5月 09, 2005
作者:
T
Tom Lane
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Update release notes for upcoming re-releases.
上级
1199026e
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
50 addition
and
6 deletion
+50
-6
doc/src/sgml/release.sgml
doc/src/sgml/release.sgml
+50
-6
未找到文件。
doc/src/sgml/release.sgml
浏览文件 @
d8c21181
<!--
<!--
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.33
5 2005/05/05 17:59:40
tgl Exp $
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.33
6 2005/05/09 00:09:45
tgl Exp $
-->
-->
<appendix id="release">
<appendix id="release">
...
@@ -10,7 +10,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.335 2005/05/05 17:59:40 tgl Exp
...
@@ -10,7 +10,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.335 2005/05/05 17:59:40 tgl Exp
<note>
<note>
<title>Release date</title>
<title>Release date</title>
<simpara>2005-05-0
5
</simpara>
<simpara>2005-05-0
9
</simpara>
</note>
</note>
<para>
<para>
...
@@ -72,6 +72,17 @@ misuse</para></listitem>
...
@@ -72,6 +72,17 @@ misuse</para></listitem>
<type>INTERNAL</> function results</para></listitem>
<type>INTERNAL</> function results</para></listitem>
<listitem><para>Guard against incorrect second parameter to
<listitem><para>Guard against incorrect second parameter to
<function>record_out</></para></listitem>
<function>record_out</></para></listitem>
<listitem><para>Repair ancient race condition that allowed a transaction to be
seen as committed for some purposes (eg SELECT FOR UPDATE) slightly sooner
than for other purposes</para>
<para>This is an extremely serious bug since it could lead to apparent
data inconsistencies being briefly visible to applications.</para></listitem>
<listitem><para>Repair race condition between relation extension and
VACUUM</para>
<para>This could theoretically have caused loss of a page's worth of
freshly-inserted data, although the scenario seems of very low probability.
There are no known cases of it having caused more than an Assert failure.
</para></listitem>
<listitem><para>Fix comparisons of <type>TIME WITH TIME ZONE</> values</para>
<listitem><para>Fix comparisons of <type>TIME WITH TIME ZONE</> values</para>
<para>
<para>
The comparison code was wrong in the case where the
The comparison code was wrong in the case where the
...
@@ -2684,7 +2695,7 @@ typedefs (Michael)</para></listitem>
...
@@ -2684,7 +2695,7 @@ typedefs (Michael)</para></listitem>
<note>
<note>
<title>Release date</title>
<title>Release date</title>
<simpara>2005-05-0
5
</simpara>
<simpara>2005-05-0
9
</simpara>
</note>
</note>
<para>
<para>
...
@@ -2795,6 +2806,17 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
...
@@ -2795,6 +2806,17 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
misuse</para></listitem>
misuse</para></listitem>
<listitem><para>Change <filename>contrib/tsearch2</> to avoid unsafe use of
<listitem><para>Change <filename>contrib/tsearch2</> to avoid unsafe use of
<type>INTERNAL</> function results</para></listitem>
<type>INTERNAL</> function results</para></listitem>
<listitem><para>Repair ancient race condition that allowed a transaction to be
seen as committed for some purposes (eg SELECT FOR UPDATE) slightly sooner
than for other purposes</para>
<para>This is an extremely serious bug since it could lead to apparent
data inconsistencies being briefly visible to applications.</para></listitem>
<listitem><para>Repair race condition between relation extension and
VACUUM</para>
<para>This could theoretically have caused loss of a page's worth of
freshly-inserted data, although the scenario seems of very low probability.
There are no known cases of it having caused more than an Assert failure.
</para></listitem>
<listitem><para>Fix comparisons of <type>TIME WITH TIME ZONE</> values</para>
<listitem><para>Fix comparisons of <type>TIME WITH TIME ZONE</> values</para>
<para>
<para>
The comparison code was wrong in the case where the
The comparison code was wrong in the case where the
...
@@ -5236,7 +5258,7 @@ DROP SCHEMA information_schema CASCADE;
...
@@ -5236,7 +5258,7 @@ DROP SCHEMA information_schema CASCADE;
<note>
<note>
<title>Release date</title>
<title>Release date</title>
<simpara>2005-05-0
5
</simpara>
<simpara>2005-05-0
9
</simpara>
</note>
</note>
<para>
<para>
...
@@ -5313,6 +5335,17 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
...
@@ -5313,6 +5335,17 @@ UPDATE pg_database SET datallowconn = false WHERE datname = 'template0';
<itemizedlist>
<itemizedlist>
<listitem><para>Change encoding function signature to prevent
<listitem><para>Change encoding function signature to prevent
misuse</para></listitem>
misuse</para></listitem>
<listitem><para>Repair ancient race condition that allowed a transaction to be
seen as committed for some purposes (eg SELECT FOR UPDATE) slightly sooner
than for other purposes</para>
<para>This is an extremely serious bug since it could lead to apparent
data inconsistencies being briefly visible to applications.</para></listitem>
<listitem><para>Repair race condition between relation extension and
VACUUM</para>
<para>This could theoretically have caused loss of a page's worth of
freshly-inserted data, although the scenario seems of very low probability.
There are no known cases of it having caused more than an Assert failure.
</para></listitem>
<listitem><para>Fix comparisons of <type>TIME WITH TIME ZONE</> values</para>
<listitem><para>Fix comparisons of <type>TIME WITH TIME ZONE</> values</para>
<para>
<para>
The comparison code was wrong in the case where the
The comparison code was wrong in the case where the
...
@@ -6511,7 +6544,7 @@ operations on bytea columns (Joe)</para></listitem>
...
@@ -6511,7 +6544,7 @@ operations on bytea columns (Joe)</para></listitem>
<note>
<note>
<title>Release date</title>
<title>Release date</title>
<simpara>2005-05-0
5
</simpara>
<simpara>2005-05-0
9
</simpara>
</note>
</note>
<para>
<para>
...
@@ -6531,6 +6564,17 @@ operations on bytea columns (Joe)</para></listitem>
...
@@ -6531,6 +6564,17 @@ operations on bytea columns (Joe)</para></listitem>
<title>Changes</title>
<title>Changes</title>
<itemizedlist>
<itemizedlist>
<listitem><para>Repair ancient race condition that allowed a transaction to be
seen as committed for some purposes (eg SELECT FOR UPDATE) slightly sooner
than for other purposes</para>
<para>This is an extremely serious bug since it could lead to apparent
data inconsistencies being briefly visible to applications.</para></listitem>
<listitem><para>Repair race condition between relation extension and
VACUUM</para>
<para>This could theoretically have caused loss of a page's worth of
freshly-inserted data, although the scenario seems of very low probability.
There are no known cases of it having caused more than an Assert failure.
</para></listitem>
<listitem><para>Fix <function>EXTRACT(EPOCH)</> for
<listitem><para>Fix <function>EXTRACT(EPOCH)</> for
<type>TIME WITH TIME ZONE</> values</para></listitem>
<type>TIME WITH TIME ZONE</> values</para></listitem>
<listitem><para>Additional buffer overrun checks in plpgsql
<listitem><para>Additional buffer overrun checks in plpgsql
...
@@ -7133,7 +7177,7 @@ since <productname>PostgreSQL</productname> 7.1.
...
@@ -7133,7 +7177,7 @@ since <productname>PostgreSQL</productname> 7.1.
<listitem><para>Make ALTER TABLE / RENAME COLUMN update column names of indexes (Brent Verner)</para></listitem>
<listitem><para>Make ALTER TABLE / RENAME COLUMN update column names of indexes (Brent Verner)</para></listitem>
<listitem><para>Fix for ALTER TABLE / ADD CONSTRAINT ... CHECK with inherited tables (Stephan Szabo)</para></listitem>
<listitem><para>Fix for ALTER TABLE / ADD CONSTRAINT ... CHECK with inherited tables (Stephan Szabo)</para></listitem>
<listitem><para>ALTER TABLE RENAME update foreign-key trigger arguments correctly (Brent Verner)</para></listitem>
<listitem><para>ALTER TABLE RENAME update foreign-key trigger arguments correctly (Brent Verner)</para></listitem>
<listitem><para>DROP AGGREGATE and COMMENT ON AGGREGATE now accept
s
an aggtype (Tom)</para></listitem>
<listitem><para>DROP AGGREGATE and COMMENT ON AGGREGATE now accept an aggtype (Tom)</para></listitem>
<listitem><para>Add automatic return type data casting for SQL functions (Tom)</para></listitem>
<listitem><para>Add automatic return type data casting for SQL functions (Tom)</para></listitem>
<listitem><para>Allow GiST indexes to handle NULLs and multikey indexes (Oleg Bartunov, Teodor Sigaev, Tom)</para></listitem>
<listitem><para>Allow GiST indexes to handle NULLs and multikey indexes (Oleg Bartunov, Teodor Sigaev, Tom)</para></listitem>
<listitem><para>Enable partial indexes (Martijn van Oosterhout)</para></listitem>
<listitem><para>Enable partial indexes (Martijn van Oosterhout)</para></listitem>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录