Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
ef110c0a
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,发现更多精彩内容 >>
提交
ef110c0a
编写于
11月 16, 2003
作者:
B
Bruce Momjian
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Update HISTORY
上级
658b58dc
变更
1
显示空白变更内容
内联
并排
Showing
1 changed file
with
22 addition
and
18 deletion
+22
-18
HISTORY
HISTORY
+22
-18
未找到文件。
HISTORY
浏览文件 @
ef110c0a
...
...
@@ -46,7 +46,7 @@
Function-inlining for simple SQL functions
Simple SQL functions can now be inlined by including their SQL
in the main query. This improves performance by eliminating
per-call overhead. That means
,
simple SQL functions now behave
per-call overhead. That means simple SQL functions now behave
like macros.
Full support for IPv6 connections and IPv6 address data types
...
...
@@ -58,11 +58,11 @@
Several people very familiar with the SSL API have overhauled
our SSL code to improve SSL key negotiation and error recovery.
Make free space map
to
efficiently reuse empty index pages, and other
Make free space map efficiently reuse empty index pages, and other
free space management improvements
In previous releases, B-tree index pages that were left empty
because of deleted rows could only be reused by rows with index
values similar to the
original rows
indexed on that page. In
values similar to the
rows originally
indexed on that page. In
7.4, "VACUUM" records empty index pages and allows them to be
reused for any future index rows.
...
...
@@ -71,12 +71,12 @@
to access information about the schema objects defined in a
database.
Cursors conform more closely
with
the SQL standard
Cursors conform more closely
to
the SQL standard
The commands "FETCH" and "MOVE" have been overhauled to conform
more closely to the SQL standard.
Cursors can exist outside transactions
These cursors are also called holdable cursors
These cursors are also called holdable cursors
.
New client-to-server protocol
The new protocol adds error codes, more status information,
...
...
@@ -124,7 +124,7 @@
Significant effort was invested to make the messages more
consistent and user-oriented. If your applications try to detect
different error conditions by parsing the error message, you are
strongly encourage
to use the new error code facility
.
strongly encourage
d to use the new error code facility instead
.
* Inner joins using the explicit JOIN syntax may behave differently
because they are now better optimized.
* A number of server configuration parameters have been renamed for
...
...
@@ -238,8 +238,8 @@ Performance Improvements
of function-allocated memory when the function call completes,
reducing the total memory used by functions.
* Improve GEQO optimizer performance (Tom)
Th
ere were several inefficiencies in the way the GEQO optimizer
managed potential query paths. This release fixes thi
s.
Th
is release fixes several inefficiencies in the way the GEQO
optimizer manages potential query path
s.
* Allow IN/NOT IN to be handled via hash tables (Tom)
* Improve NOT IN (subquery) performance (Tom)
* Allow most IN subqueries to be processed as joins (Tom)
...
...
@@ -430,8 +430,9 @@ Utility Command Changes
deleted on transaction commit.
* Allow cursors outside transactions using WITH HOLD (Neil)
In previous releases, cursors were removed at the end of the
transaction. Using WITH HOLD, the current release allows cursors
to remain readable after the creating transaction.
transaction that created them. Cursors can now be created with the
WITH HOLD option, which allows them to continue to be accessed
after the creating transaction has committed.
* FETCH 0 and MOVE 0 now do nothing (Bruce)
In previous releases, FETCH 0 fetched all remaining rows, and MOVE
0 moved to the end of the cursor.
...
...
@@ -441,10 +442,12 @@ Utility Command Changes
In prior releases, the row count returned by "FETCH" and "MOVE"
did not accurately reflect the number of rows processed.
* Properly handle SCROLL with cursors, or report an error (Neil)
Certain cursors can not be fetched backwards optimally. By
specifying SCROLL, extra work will be performed to guarantee that
the cursor can be fetched in reverse or random order.
* Implement SQL-compatible option FIRST, LAST, ABSOLUTE n, RELATIVE
Allowing random access (both forward and backward scrolling) to
some kinds of queries cannot be done without some additional work.
If SCROLL is specified when the cursor is created, this additional
work will be performed. Furthermore, if the cursor has been
created with NO SCROLL, no random access is allowed.
* Implement SQL-compatible options FIRST, LAST, ABSOLUTE n, RELATIVE
n for "FETCH" and "MOVE" (Tom)
* Allow "EXPLAIN" on "DECLARE CURSOR" (Tom)
* Allow "CLUSTER" to use index marked as pre-clustered by default
...
...
@@ -460,8 +463,9 @@ Utility Command Changes
* Recover from "COPY" failure cleanly (Tom)
* Prevent possible memory leaks in "COPY" (Tom)
* Make "TRUNCATE" transaction-safe (Rod)
"TRUNCATE" can now be used inside a transaction, and rolled back
if the transaction aborts.
"TRUNCATE" can now be used inside a transaction. If the
transaction aborts, the changes made by the "TRUNCATE" are
automatically rolled back.
* Allow prepare/bind of utility commands like "FETCH" and "EXPLAIN"
(Tom)
* Add "EXPLAIN EXECUTE" (Neil)
...
...
@@ -758,8 +762,8 @@ Contrib Changes
* Fix bug in metaphone() in fuzzystrmatch
* Improve adddepend (Rod)
* Update spi/timetravel (Böjthe Zoltán)
* Fix dbase "-s" option and improve non-ASCII handling (Thomas
Behr,
Márcio Smiderle)
* Fix dbase "-s" option and improve non-ASCII handling (Thomas
Behr,
Márcio Smiderle)
* Remove array module because features now included by default (Joe)
_________________________________________________________________
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录