提交 7c0f07c9 编写于 作者: P Pengcheng Tang

Fix the typo for external table dump

The typo is from the dumping based on object types(i.e,
index/function/trigger/table/data), but currently gpdb
does not support this feature ported from postgres.

Initially planned to remove the related dead code, but
as we do the merge of the upstream postgres, I decide to
save the code to minimize the diff and effort in case
we want to support such in future.
上级 65400193
......@@ -2108,7 +2108,7 @@ _tocEntryRequired(TocEntry *te, RestoreOptions *ropt, bool include_acls)
if (ropt->selTypes)
{
if (strcmp(te->desc, "TABLE") == 0 ||
strcmp(te->desc, "EXTNRNAL TABLE") == 0 ||
strcmp(te->desc, "EXTERNAL TABLE") == 0 ||
strcmp(te->desc, "FOREIGN TABLE") == 0 ||
strcmp(te->desc, "TABLE DATA") == 0)
{
......
......@@ -2070,7 +2070,7 @@ _tocEntryRequired(TocEntry *te, RestoreOptions *ropt, bool include_acls)
if (ropt->selTypes)
{
if (strcmp(te->desc, "TABLE") == 0 ||
strcmp(te->desc, "EXTNRNAL TABLE") == 0 ||
strcmp(te->desc, "EXTERNAL TABLE") == 0 ||
strcmp(te->desc, "FOREIGN TABLE") == 0 ||
strcmp(te->desc, "TABLE DATA") == 0)
{
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册