Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
a5269221
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,发现更多精彩内容 >>
提交
a5269221
编写于
2月 16, 2000
作者:
B
Bruce Momjian
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
README not needed anymore.
上级
bf566b20
变更
3
隐藏空白更改
内联
并排
Showing
3 changed file
with
6 addition
and
80 deletion
+6
-80
src/bin/initdb/Makefile
src/bin/initdb/Makefile
+2
-2
src/bin/initdb/initdb.sh
src/bin/initdb/initdb.sh
+4
-5
src/bin/pg_dump/README
src/bin/pg_dump/README
+0
-73
未找到文件。
src/bin/initdb/Makefile
浏览文件 @
a5269221
...
...
@@ -7,7 +7,7 @@
#
#
# IDENTIFICATION
# $Header: /cvsroot/pgsql/src/bin/initdb/Makefile,v 1.1
6 2000/01/15 18:30:31 petere
Exp $
# $Header: /cvsroot/pgsql/src/bin/initdb/Makefile,v 1.1
7 2000/02/16 21:25:59 momjian
Exp $
#
#-------------------------------------------------------------------------
...
...
@@ -20,7 +20,7 @@ initdb: initdb.sh
sed
-e
's/__MULTIBYTE__/
$(MULTIBYTE)
/g'
< initdb.sh
>
initdb
install
:
initdb
$(INSTALL)
$(INSTL_EXE_OPTS)
$+
$(BINDIR)
$(INSTALL)
$(INSTL_EXE_OPTS)
$+
$(BINDIR)
/
$+
clean
:
rm
-f
initdb
...
...
src/bin/initdb/initdb.sh
浏览文件 @
a5269221
...
...
@@ -26,7 +26,7 @@
#
#
# IDENTIFICATION
# $Header: /cvsroot/pgsql/src/bin/initdb/Attic/initdb.sh,v 1.8
5 2000/02/09 00:21:49 petere
Exp $
# $Header: /cvsroot/pgsql/src/bin/initdb/Attic/initdb.sh,v 1.8
6 2000/02/16 21:25:59 momjian
Exp $
#
#-------------------------------------------------------------------------
...
...
@@ -605,10 +605,9 @@ echo "VACUUM ANALYZE" \
|
"
$PGPATH
"
/postgres
$PGSQL_OPT
template1
>
/dev/null
||
exit_nicely
echo
echo
"
$CMDNAME
completed successfully. You can now start the database server."
echo
"
$PGPATH
/postmaster -D
$PGDATA
"
echo
"or"
echo
"
$PGPATH
/pg_ctl -D
$PGDATA
start"
echo
"Success. You can now start the database server using"
echo
"
$PGPATH
/postmaster -D
$PGDATA
or"
echo
"
$PGPATH
/pg_ctl -D
$PGDATA
start"
echo
exit
0
src/bin/pg_dump/README
已删除
100644 → 0
浏览文件 @
bf566b20
pg_dump is a utility for dumping out a postgres database into a script
file containing query commands. The script files are in a ASCII
format and can be used to reconstruct the database, even on other
machines and other architectures. pg_dump will produce the queries
necessary to re-generate all user-defined types, functions, tables,
indices, aggregates, and operators. In addition, all the data is
copied out in ASCII format so that it can be readily copied in again.
To build:
% gmake clean install
This version of the program will read in your postgreSQL database and
output the schema and the data tuples in SQL. The dumps are useful
for moving from one postgreSQL installation to another.
How to use pg_dump:
-------------------
The command line options are fairly self explanatory. Use -help to
see the command line options. recommend using -v to get
more verbose descriptions of what pg_dump is doing.
After running pg_dump, one should examine the output script file for any
warnings, especially in light of the limitations listed below.
A typical use of pg_dump:
% pg_dump -v -f oldDB.dump oldDB
% createdb newDB
% psql newDB < oldDB.dump
Caveats and limitations:
------------------------
pg_dump has a few limitations. The limitations mostly stem from
difficulty in extracting certain meta-information from the system
catalogs.
rules and views:
pg_dump does not understand user-defined rules and views and
will fail to dump them properly. (This is due to the fact that
rules are stored as plans in the catalogs and not textually)
partial indices:
pg_dump does not understand partial indices. (The reason is
the same as above. Partial index predicates are stored as plans)
large objects:
pg_dump does not handle large objects. Large
objects are ignored and must be dealt with manually.
oid preservation:
pg_dump does not preserve oid's while dumping. If you have
stored oid's explicitly in tables in user-defined attributes,
and are using them as keys, then the output scripts will not
regenerate your database correctly.
pg_dump requires postgres95 beta0.03 or later.
Bug-reporting
--------------
If you should find a problem with pg_dump, it is very important that
you provide a (small) sample database which illustrates the problem.
Please send bugs, questions, and feedback to the
postgres95@postgres95.vnet.net
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录