Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
8bd1cbb8
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,发现更多精彩内容 >>
提交
8bd1cbb8
编写于
11月 03, 2005
作者:
N
Neil Conway
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Some minor improvements to the CE docs. Also fix a bit of SGML markup
elsewhere.
上级
99d48695
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
55 addition
and
42 deletion
+55
-42
doc/src/sgml/ddl.sgml
doc/src/sgml/ddl.sgml
+52
-39
doc/src/sgml/ref/create_role.sgml
doc/src/sgml/ref/create_role.sgml
+3
-3
未找到文件。
doc/src/sgml/ddl.sgml
浏览文件 @
8bd1cbb8
<
!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.4
6 2005/11/01 23:19:05
neilc Exp $ -->
<
!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.4
7 2005/11/03 00:51:43
neilc Exp $ -->
<
chapter
id
=
"ddl"
>
<
title
>
Data
Definition
</
title
>
...
...
@@ -1406,32 +1406,42 @@ SELECT * from cities*;
</listitem>
</itemizedlist>
The benefits will normally be worthwhile only when a data table would
otherwise be very large. That is for you to judge, though would not
usually be lower than the size of physical RAM on the database server.
The benefits will normally be worthwhile only when a table would
otherwise be very large. The exact point at which a table will
benefit from partitioning depends on the application, although the
size of the table should usually exceed the physical memory of the
database server.
</para>
<para>
In <productname>PostgreSQL</productname> &version;, the following
partitioning types are supported
:
The following partitioning types are supported by
<productname>PostgreSQL</productname> &version;
:
<itemizedlist>
<listitem>
<para>
"Range Partitioning" where the table is partitioned along a
"range" defined by a single column or set of columns, with no
overlap between partitions. Examples might be a date range or a
range of identifiers for particular business objects.
</para>
</listitem>
<variablelist>
<varlistentry>
<term>Range Partitioning</term>
<listitem>
<para>
"List Partitioning" where the table is partitioned by
explicitly listing which values relate to each partition.
</para>
</listitem>
</itemizedlist>
<listitem>
<para>
The table is partitioned along a <quote>range</quote> defined
by a single column or set of columns, with no overlap between
partitions. Examples might be a date range or a range of
identifiers for particular business objects.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>List Partitioning</term>
<listitem>
<para>
The table is partitioned by explicitly listing which values
relate to each partition.
</para>
</listitem>
</varlistentry>
</variablelist>
Hash partitioning is not currently supported.
</para>
...
...
@@ -1471,8 +1481,7 @@ SELECT * from cities*;
<para>
We will refer to the child tables as partitions, though they
are in every way just normal <productname>PostgreSQL</>
tables.
are in every way normal <productname>PostgreSQL</> tables.
</para>
</listitem>
...
...
@@ -1485,15 +1494,16 @@ SELECT * from cities*;
for constraint exclusion. Simple examples would be:
<programlisting>
CHECK ( x = 1 )
CHECK ( county IN (
'
Oxfordshire
','
Buckinghamshire
','
Warwickshire
'
))
CHECK ( county IN (
'
Oxfordshire
','
Buckinghamshire
','
Warwickshire
'
))
CHECK ( outletID BETWEEN 1 AND 99 )
</programlisting>
These can be linked together with boolean operators AND and OR to
form complex constraints. Note that there is no difference in syntax
between Range and List Partitioning mechanisms; those terms are
descriptive only. Ensure that the set of values in each child table
do not overlap.
These can be linked together with the boolean operators
<literal>AND</literal> and <literal>OR</literal> to form
complex constraints. Note that there is no difference in
syntax between range and list partitioning; those terms are
descriptive only. Ensure that the set of values in each child
table do not overlap.
</para>
</listitem>
...
...
@@ -1712,19 +1722,22 @@ DO INSTEAD
<listitem>
<para>
For some datatypes you must explicitly coerce the constant values
into the datatype of the column. The following constraint will
work if x is an INTEGER datatype, but not if x is BIGINT datatype.
For some datatypes you must explicitly coerce the constant
values into the datatype of the column. The following constraint
will work if <varname>x</varname> is an <type>integer</type>
datatype, but not if <varname>x</varname> is a
<type>bigint</type>:
<programlisting>
CHECK ( x = 1 )
</programlisting>
For
BIGINT
we must use a constraint like:
For
<type>bigint</type>
we must use a constraint like:
<programlisting>
CHECK ( x = 1::bigint )
</programlisting>
The issue is not restricted to BIGINT datatypes but can occur whenever
the default datatype of the constant does not match the datatype of
the column to which it is being compared.
The problem is not limited to the <type>bigint</type> datatype
— it can occur whenever the default datatype of the
constant does not match the datatype of the column to which it
is being compared.
</para>
</listitem>
...
...
@@ -2312,8 +2325,8 @@ REVOKE ALL ON accounts FROM PUBLIC;
</indexterm>
<para>
To create a schema, use the command <
literal
>CREATE
SCHEMA</
literal
>. Give the schema a name of your choice. For
To create a schema, use the command <
command
>CREATE
SCHEMA</
command
>. Give the schema a name of your choice. For
example:
<programlisting>
CREATE SCHEMA myschema;
...
...
doc/src/sgml/ref/create_role.sgml
浏览文件 @
8bd1cbb8
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/create_role.sgml,v 1.
3 2005/08/14 23:35:38 tgl
Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/create_role.sgml,v 1.
4 2005/11/03 00:51:43 neilc
Exp $
PostgreSQL documentation
-->
...
...
@@ -112,7 +112,7 @@ where <replaceable class="PARAMETER">option</replaceable> can be:
<listitem>
<para>
These clauses determine whether a role will be permitted to
create new roles (that is, execute <
literal>CREATE ROLE</literal
>).
create new roles (that is, execute <
command>CREATE ROLE</command
>).
A role with <literal>CREATEROLE</literal> privilege can also alter
and drop other roles.
If not specified,
...
...
@@ -374,7 +374,7 @@ CREATE ROLE jonathan LOGIN;
<programlisting>
CREATE USER davide WITH PASSWORD 'jw8s0F4';
</programlisting>
(<
literal>CREATE USER</> is the same as <literal
>CREATE ROLE</> except
(<
command>CREATE USER</> is the same as <command
>CREATE ROLE</> except
that it implies <literal>LOGIN</>.)
</para>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录