Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
08674935
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,发现更多精彩内容 >>
提交
08674935
编写于
1月 31, 2007
作者:
B
Bruce Momjian
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Document need for periodic REINDEX in VACUUM FULL cases.
上级
1a628134
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
6 addition
and
5 deletion
+6
-5
doc/src/sgml/maintenance.sgml
doc/src/sgml/maintenance.sgml
+2
-4
doc/src/sgml/ref/vacuum.sgml
doc/src/sgml/ref/vacuum.sgml
+4
-1
未找到文件。
doc/src/sgml/maintenance.sgml
浏览文件 @
08674935
<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.6
6 2007/01/16 18:26:02 alvherre
Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.6
7 2007/01/31 04:13:22 momjian
Exp $ -->
<chapter id="maintenance">
<chapter id="maintenance">
<title>Routine Database Maintenance Tasks</title>
<title>Routine Database Maintenance Tasks</title>
...
@@ -615,9 +615,7 @@ analyze threshold = analyze base threshold + analyze scale factor * number of tu
...
@@ -615,9 +615,7 @@ analyze threshold = analyze base threshold + analyze scale factor * number of tu
for inefficient use of space: if all but a few index keys on a page have
for inefficient use of space: if all but a few index keys on a page have
been deleted, the page remains allocated. So a usage pattern in which all
been deleted, the page remains allocated. So a usage pattern in which all
but a few keys in each range are eventually deleted will see poor use of
but a few keys in each range are eventually deleted will see poor use of
space. The potential for bloat is not indefinite — at worst there
space. For such usage patterns, periodic reindexing is recommended.
will be one key per page — but it may still be worthwhile to schedule
periodic reindexing for indexes that have such usage patterns.
</para>
</para>
<para>
<para>
...
...
doc/src/sgml/ref/vacuum.sgml
浏览文件 @
08674935
<!--
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.4
5 2006/12/27 14:55:17
momjian Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.4
6 2007/01/31 04:13:22
momjian Exp $
PostgreSQL documentation
PostgreSQL documentation
-->
-->
...
@@ -167,6 +167,9 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">
...
@@ -167,6 +167,9 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">
most of the rows in a table and would like the table to physically shrink
most of the rows in a table and would like the table to physically shrink
to occupy less disk space. <command>VACUUM FULL</command> will usually
to occupy less disk space. <command>VACUUM FULL</command> will usually
shrink the table more than a plain <command>VACUUM</command> would.
shrink the table more than a plain <command>VACUUM</command> would.
The <option>FULL</option> option does not shrink indexes; a periodic
<command>REINDEX</> is still recommended. In fact, it is often faster
to drop all indexes, <command>VACUUM FULL</>, and recreate the indexes.
</para>
</para>
<para>
<para>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录