Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
c5eabafb
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,发现更多精彩内容 >>
提交
c5eabafb
编写于
10月 14, 2008
作者:
A
Alvaro Herrera
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Ensure that CLUSTER leaves the toast table and index with consistent names,
by renaming the new copies after the catalog games.
上级
a303e4dc
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
32 addition
and
1 deletion
+32
-1
src/backend/commands/cluster.c
src/backend/commands/cluster.c
+32
-1
未找到文件。
src/backend/commands/cluster.c
浏览文件 @
c5eabafb
...
...
@@ -11,7 +11,7 @@
*
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/commands/cluster.c,v 1.17
7 2008/06/19 00:46:04
alvherre Exp $
* $PostgreSQL: pgsql/src/backend/commands/cluster.c,v 1.17
8 2008/10/14 17:19:50
alvherre Exp $
*
*-------------------------------------------------------------------------
*/
...
...
@@ -29,6 +29,7 @@
#include "catalog/index.h"
#include "catalog/indexing.h"
#include "catalog/namespace.h"
#include "catalog/pg_namespace.h"
#include "catalog/toasting.h"
#include "commands/cluster.h"
#include "commands/tablecmds.h"
...
...
@@ -568,6 +569,7 @@ rebuild_relation(Relation OldHeap, Oid indexOid)
char
NewHeapName
[
NAMEDATALEN
];
TransactionId
frozenXid
;
ObjectAddress
object
;
Relation
newrel
;
/* Mark the correct index as clustered */
mark_index_clustered
(
OldHeap
,
indexOid
);
...
...
@@ -622,6 +624,35 @@ rebuild_relation(Relation OldHeap, Oid indexOid)
* because reindex_relation does it.
*/
reindex_relation
(
tableOid
,
false
);
/*
* At this point, everything is kosher except that the toast table's name
* corresponds to the temporary table. The name is irrelevant to
* the backend because it's referenced by OID, but users looking at the
* catalogs could be confused. Rename it to prevent this problem.
*
* Note no lock required on the relation, because we already hold an
* exclusive lock on it.
*/
newrel
=
heap_open
(
tableOid
,
NoLock
);
if
(
OidIsValid
(
newrel
->
rd_rel
->
reltoastrelid
))
{
char
NewToastName
[
NAMEDATALEN
];
Relation
toastrel
;
/* rename the toast table ... */
snprintf
(
NewToastName
,
NAMEDATALEN
,
"pg_toast_%u"
,
tableOid
);
RenameRelationInternal
(
newrel
->
rd_rel
->
reltoastrelid
,
NewToastName
,
PG_TOAST_NAMESPACE
);
/* ... and its index too */
toastrel
=
relation_open
(
newrel
->
rd_rel
->
reltoastrelid
,
AccessShareLock
);
snprintf
(
NewToastName
,
NAMEDATALEN
,
"pg_toast_%u_index"
,
tableOid
);
RenameRelationInternal
(
toastrel
->
rd_rel
->
reltoastidxid
,
NewToastName
,
PG_TOAST_NAMESPACE
);
relation_close
(
toastrel
,
AccessShareLock
);
}
relation_close
(
newrel
,
NoLock
);
}
/*
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录