Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
f22f57ca
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,发现更多精彩内容 >>
提交
f22f57ca
编写于
5月 13, 1997
作者:
B
Bruce Momjian
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Update manual pages for vacuum and create index for Vadim.
上级
1e790e20
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
15 addition
and
9 deletion
+15
-9
src/man/create_index.l
src/man/create_index.l
+8
-7
src/man/vacuum.l
src/man/vacuum.l
+7
-2
未找到文件。
src/man/create_index.l
浏览文件 @
f22f57ca
.\" This is -*-nroff-*-
.\" XXX standard disclaimer belongs here....
.\" $Header: /cvsroot/pgsql/src/man/Attic/create_index.l,v 1.
4 1997/01/13 17:22:25
momjian Exp $
.\" $Header: /cvsroot/pgsql/src/man/Attic/create_index.l,v 1.
5 1997/05/13 04:41:51
momjian Exp $
.TH "CREATE INDEX" SQL 11/05/95 PostgreSQL PostgreSQL
.SH NAME
create index \(em construct a secondary index
...
...
@@ -8,7 +8,7 @@ create index \(em construct a secondary index
.nf
\fBcreate\fR [\fBunique\fR] \fBindex\fR index-name
\fBon\fR classname [\fBusing\fR am-name]
\fB(\fR attname [type_class\fB] )\fR
\fB(\fR attname
, ...
[type_class\fB] )\fR
\fBcreate\fR [\fBunique\fR] \fBindex\fR index-name
\fBon\fR classname [\fBusing\fR am-name]
...
...
@@ -22,12 +22,12 @@ This command constructs an index called
is the name of the access method which is used for the index.
The default access method is btree.
.PP
In the first syntax shown above, the key field
for the index is
specified as a
n attribute name and
an associated
In the first syntax shown above, the key field
s for the index are
specified as a
ttribute names. It may also have
an associated
.IR "operator class" .
An operator class is used to specify the operators to be used for a
particular index.
For example, a btree index on four-byte integers
would use the
particular index.
For example, a btree index on four-byte integers
would use the
.IR int4_ops
class; this operator class includes comparison functions for four-byte
integers.
...
...
@@ -40,7 +40,7 @@ result of a user-defined function
applied to one or more attributes of a single class. These
.IR "functional indices"
are primarily useful in two situations. First, functional indices can
be used to simulate multikey indices. That is, the user can define a
be used to simulate multi
-
key indices. That is, the user can define a
new base type (a simple combination of, say, \*(lqoid\*(rq and
\*(lqint2\*(rq) and the associated functions and operators on this new
type such that the access method can use it. Once this has been done,
...
...
@@ -260,6 +260,7 @@ and
represent the use of
.IR "functional indices"
to simulate multi-key indices.
These are no longer needed now that multi-key indexes are supported.
.PP
The Postgres query optimizer will consider using btree indices in a scan
whenever an indexed attribute is involved in a comparison using one of:
...
...
src/man/vacuum.l
浏览文件 @
f22f57ca
.\" This is -*-nroff-*-
.\" XXX standard disclaimer belongs here....
.\" $Header: /cvsroot/pgsql/src/man/Attic/vacuum.l,v 1.
3 1997/01/13 03:45:33
momjian Exp $
.\" $Header: /cvsroot/pgsql/src/man/Attic/vacuum.l,v 1.
4 1997/05/13 04:41:54
momjian Exp $
.TH VACUUM SQL 11/05/95 PostgreSQL PostgreSQL
.SH NAME
vacuum \(em vacuum a database
.SH SYNOPSIS
.nf
\fBvacuum [verbose] [
\fPtable
\fB]\fP
\fBvacuum [verbose] [
analyze] [\fPtable [(column,...)]
\fB]\fP
.fi
.SH DESCRIPTION
.BR Vacuum
...
...
@@ -20,6 +20,11 @@ periodically will increase Postgres's speed in processing user queries.
.PP
\fBverbose\fP prints a detailed vacuum activity report for each table.
.PP
\fBanalyze\fP also updates column statistics used by the optimizer to
determine the most efficient way to execute a query.
The statistics represent the disbursion of the data in each column.
This information is valuable when several execution paths are possible.
.PP
The open database is the one that is vacuumed.
.PP
We recommend that production databases be vacuumed nightly, in order
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录