Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
5458bd2f
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,发现更多精彩内容 >>
提交
5458bd2f
编写于
2月 14, 2003
作者:
B
Bruce Momjian
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Update FAQ.
上级
c5f8cbf9
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
19 addition
and
22 deletion
+19
-22
doc/FAQ
doc/FAQ
+1
-1
doc/src/FAQ/FAQ.html
doc/src/FAQ/FAQ.html
+18
-21
未找到文件。
doc/FAQ
浏览文件 @
5458bd2f
Frequently Asked Questions (FAQ) for PostgreSQL
Last updated:
Mon Jan 27 01:24:42
EST 2003
Last updated:
Thu Feb 13 23:07:35
EST 2003
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
...
...
doc/src/FAQ/FAQ.html
浏览文件 @
5458bd2f
...
...
@@ -10,7 +10,7 @@
alink=
"#0000ff"
>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<P>
Last updated: Thu
Dec 5 00:47:26 EST 2002
</P>
<P>
Last updated: Thu
Feb 13 23:07:35 EST 2003
</P>
<P>
Current maintainer: Bruce Momjian (
<A
href=
"mailto:pgman@candle.pha.pa.us"
>
pgman@candle.pha.pa.us
</A>
)
<BR>
...
...
@@ -318,7 +318,7 @@
<H4><A
name=
"1.7"
>
1.7
</A>
) What is the latest release?
</H4>
<P>
The latest release of PostgreSQL is version 7.
2.3
.
</P>
<P>
The latest release of PostgreSQL is version 7.
3.1
.
</P>
<P>
We plan to have major releases every four months.
</P>
...
...
@@ -536,8 +536,8 @@
interface?
</H4>
Yes, there are several graphical interfaces to PostgreSQL available.
These include PgAccess
<a
href=
"http://www.pgaccess.
com
"
>
http://www.pgaccess.
com
</a>
), PgAdmin II (
<a
These include PgAccess
<a
href=
"http://www.pgaccess.
org
"
>
http://www.pgaccess.
org
</a>
), PgAdmin II (
<a
href=
"http://www.pgadmin.org"
>
http://www.pgadmin.org
</a>
,
Win32-only), RHDB Admin (
<a
href=
"http://sources.redhat.com/rhdb/"
>
http://sources.redhat.com/rhdb/
...
...
@@ -547,10 +547,6 @@
http://phppgadmin.sourceforge.net/
</a>
), a web-based interface to
PostgreSQL.
<P>
We have a nice graphical user interface called PgAccess which can
also be used as a report generator. The Web page is
<A
href=
"http://www.pgaccess.org/"
>
http://www.pgaccess.org/
</A>
.
</P>
<H4><A
name=
"2.4"
>
2.4
</A>
) What languages are able to communicate with
PostgreSQL?
</H4>
...
...
@@ -757,11 +753,6 @@
the number of allowed backend processes is so your system won't run
out of resources.
</P>
<P>
In PostgreSQL versions prior to 6.5, the maximum number of
backends was 64, and changing it required a rebuild after altering
the MaxBackendId constant in
<I>
include/storage/sinvaladt.h
</I>
.
</P>
<H4><A
name=
"3.9"
>
3.9
</A>
) What is in the
<I>
pgsql_tmp
</I>
directory?
</H4>
<P>
This directory contains temporary files generated by the query
...
...
@@ -947,6 +938,10 @@
LIMIT 1;
</PRE>
<P>
If you believe the optimizer is incorrect in choosing a
sequential scan, use
<CODE>
SET enable_seqscan TO 'off'
</CODE>
and
run tests to see if an index scan is indeed faster.
</P>
<P>
When using wild-card operators such as
<SMALL>
LIKE
</SMALL>
or
<I>
~
</I>
, indexes can only be used in certain circumstances:
</P>
<UL>
...
...
@@ -1039,10 +1034,10 @@
<PRE>
Type Internal Name Notes
--------------------------------------------------
"char" char 1 character
CHAR(n) bpchar blank padded to the specified fixed length
VARCHAR(n) varchar size specifies maximum length, no padding
CHAR(n) bpchar blank padded to the specified fixed length
TEXT text no specific upper limit on length
"char" char one character
BYTEA bytea variable-length byte array (null-byte safe)
</PRE>
...
...
@@ -1056,11 +1051,13 @@ BYTEA bytea variable-length byte array (null-byte safe)
stored out-of-line by
<SMALL>
TOAST
</SMALL>
, so the space on disk
might also be less than expected.
</P>
<P><SMALL>
CHAR(n)
</SMALL>
is best when storing strings that are
usually the same length.
<SMALL>
VARCHAR(n)
</SMALL>
is best when
storing variable-length strings but it limits how long a string can
be.
<SMALL>
TEXT
</SMALL>
is for strings of unlimited length, maximum
1 gigabyte.
<SMALL>
BYTEA
</SMALL>
is for storing binary data,
<SMALL>
VARCHAR(n)
</SMALL>
is best when storing variable-length
strings and it limits how long a string can be.
<SMALL>
TEXT
</SMALL>
is for strings of unlimited length, with a maximum of one gigabyte.
<P><SMALL>
CHAR(n)
</SMALL>
is for storing strings that are all the
same length.
<SMALL>
CHAR(n)
</SMALL>
pads with blanks to the specified
length, while
<SMALL>
VARCHAR(n)
</SMALL>
only stores the characters
supplied.
<SMALL>
BYTEA
</SMALL>
is for storing binary data,
particularly values that include
<SMALL>
NULL
</SMALL>
bytes. These
types have similar performance characteristics.
</P>
...
...
@@ -1286,7 +1283,7 @@ BYTEA bytea variable-length byte array (null-byte safe)
</PRE>
For this to be fast,
<CODE>
subcol
</CODE>
should be an indexed column.
We hope to fix this limitation in a future release
.
This preformance problem will be fixed in 7.4
.
<H4><A
name=
"4.23"
>
4.23
</A>
) How do I perform an outer join?
</H4>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录