Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
8c05ca77
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,发现更多精彩内容 >>
提交
8c05ca77
编写于
6月 13, 2005
作者:
N
Neil Conway
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
SGML cleanup: consistently use "endterm" in <xref>s that link to the
reference page for SQL commands, so that the link text is italicized.
上级
a2fb7b8a
变更
8
隐藏空白更改
内联
并排
Showing
8 changed file
with
59 addition
and
50 deletion
+59
-50
doc/src/sgml/ddl.sgml
doc/src/sgml/ddl.sgml
+20
-18
doc/src/sgml/func.sgml
doc/src/sgml/func.sgml
+2
-2
doc/src/sgml/maintenance.sgml
doc/src/sgml/maintenance.sgml
+8
-7
doc/src/sgml/manage-ag.sgml
doc/src/sgml/manage-ag.sgml
+8
-6
doc/src/sgml/mvcc.sgml
doc/src/sgml/mvcc.sgml
+4
-3
doc/src/sgml/query.sgml
doc/src/sgml/query.sgml
+3
-2
doc/src/sgml/ref/psql-ref.sgml
doc/src/sgml/ref/psql-ref.sgml
+8
-8
doc/src/sgml/runtime.sgml
doc/src/sgml/runtime.sgml
+6
-4
未找到文件。
doc/src/sgml/ddl.sgml
浏览文件 @
8c05ca77
<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.4
0 2005/03/13 09:36:30
neilc Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.4
1 2005/06/13 02:40:01
neilc Exp $ -->
<chapter id="ddl">
<title>Data Definition</title>
...
...
@@ -1540,14 +1540,14 @@ ALTER TABLE products RENAME TO items;
There are several different privileges: <literal>SELECT</>,
<literal>INSERT</>, <literal>UPDATE</>, <literal>DELETE</>,
<literal>RULE</>, <literal>REFERENCES</>, <literal>TRIGGER</>,
<literal>CREATE</>, <literal>TEMPORARY</>, <literal>EXECUTE</>,
and
<literal>USAGE</>. The privileges applicable to a particular
<literal>CREATE</>, <literal>TEMPORARY</>, <literal>EXECUTE</>,
and
<literal>USAGE</>. The privileges applicable to a particular
object vary depending on the object's type (table, function, etc).
For complete
information on the different types of privileges supported by
<
productname>PostgreSQL</productname>, refer to th
e
<xref linkend="sql-grant"> reference page. The following sections
and chapters will also show you how
those privileges are used.
For complete
information on the different types of privileges
supported by <productname>PostgreSQL</productname>, refer to the
<
xref linkend="sql-grant" endterm="sql-grant-title"> referenc
e
page. The following sections and chapters will also show you how
those privileges are used.
</para>
<para>
...
...
@@ -1558,8 +1558,9 @@ ALTER TABLE products RENAME TO items;
<note>
<para>
To change the owner of a table, index, sequence, or view, use the
<xref linkend="sql-altertable"> command. There are corresponding
<literal>ALTER</> commands for other object types.
<xref linkend="sql-altertable" endterm="sql-altertable-title">
command. There are corresponding <literal>ALTER</> commands for
other object types.
</para>
</note>
...
...
@@ -1596,14 +1597,15 @@ REVOKE ALL ON accounts FROM PUBLIC;
</para>
<para>
Ordinarily, only the object's owner (or a superuser) can grant or revoke
privileges on an object. However, it is possible to grant a privilege
<quote>with grant option</>, which gives the recipient the right to
grant it in turn to others. If the grant option is subsequently revoked
then all who received the privilege from that recipient (directly or
through a chain of grants) will lose the privilege. For details see
the <xref linkend="sql-grant"> and <xref linkend="sql-revoke"> reference
pages.
Ordinarily, only the object's owner (or a superuser) can grant or
revoke privileges on an object. However, it is possible to grant a
privilege <quote>with grant option</>, which gives the recipient
the right to grant it in turn to others. If the grant option is
subsequently revoked then all who received the privilege from that
recipient (directly or through a chain of grants) will lose the
privilege. For details see the <xref linkend="sql-grant"
endterm="sql-grant-title"> and <xref linkend="sql-revoke"
endterm="sql-revoke-title"> reference pages.
</para>
</sect1>
...
...
doc/src/sgml/func.sgml
浏览文件 @
8c05ca77
<!--
$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.25
3 2005/06/09 16:35:08 momjian
Exp $
$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.25
4 2005/06/13 02:40:04 neilc
Exp $
PostgreSQL documentation
-->
...
...
@@ -8152,7 +8152,7 @@ select current_date + s.a as dates from generate_series(0,14,7) as s(a);
<para>
The <function>session_user</function> is normally the user who initiated
the current database connection; but superusers can change this setting
with <xref linkend="sql-set-session-authorization">.
with <xref linkend="sql-set-session-authorization"
endterm="sql-set-session-authorization-title"
>.
The <function>current_user</function> is the user identifier
that is applicable for permission checking. Normally, it is equal
to the session user, but it changes during the execution of
...
...
doc/src/sgml/maintenance.sgml
浏览文件 @
8c05ca77
<!--
$PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.4
3 2005/05/10 22:27:29 momjian
Exp $
$PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.4
4 2005/06/13 02:40:04 neilc
Exp $
-->
<chapter id="maintenance">
...
...
@@ -74,12 +74,13 @@ $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.43 2005/05/10 22:27:29 momj
</listitem>
</orderedlist>
The frequency and scope of the <command>VACUUM</> operations performed for each of
these reasons will vary depending on the needs of each site.
Therefore, database administrators must understand these issues and
develop an appropriate maintenance strategy. This section concentrates
on explaining the high-level issues; for details about command syntax
and so on, see the <xref linkend="sql-vacuum"> reference page.
The frequency and scope of the <command>VACUUM</> operations
performed for each of these reasons will vary depending on the
needs of each site. Therefore, database administrators must
understand these issues and develop an appropriate maintenance
strategy. This section concentrates on explaining the high-level
issues; for details about command syntax and so on, see the <xref
linkend="sql-vacuum" endterm="sql-vacuum-title"> reference page.
</para>
<para>
...
...
doc/src/sgml/manage-ag.sgml
浏览文件 @
8c05ca77
<!--
$PostgreSQL: pgsql/doc/src/sgml/manage-ag.sgml,v 2.4
0 2005/01/08 22:13:34 tgl
Exp $
$PostgreSQL: pgsql/doc/src/sgml/manage-ag.sgml,v 2.4
1 2005/06/13 02:40:04 neilc
Exp $
-->
<chapter id="managing-databases">
...
...
@@ -88,7 +88,7 @@ SELECT datname FROM pg_database;
<para>
Databases are created with the SQL command
<xref linkend="sql-createdatabase">:<indexterm><primary>CREATE
<xref linkend="sql-createdatabase"
endterm="sql-createdatabase-title"
>:<indexterm><primary>CREATE
DATABASE</></>
<synopsis>
CREATE DATABASE <replaceable>name</>;
...
...
@@ -314,7 +314,7 @@ ALTER DATABASE mydb SET geqo TO off;
<para>
Databases are destroyed with the command
<xref linkend="sql-dropdatabase">:<indexterm><primary>DROP DATABASE</></>
<xref linkend="sql-dropdatabase"
endterm="sql-dropdatabase-title"
>:<indexterm><primary>DROP DATABASE</></>
<synopsis>
DROP DATABASE <replaceable>name</>;
</synopsis>
...
...
@@ -379,7 +379,8 @@ dropdb <replaceable class="parameter">dbname</replaceable>
</para>
<para>
To define a tablespace, use the <xref linkend="sql-createtablespace">
To define a tablespace, use the <xref
linkend="sql-createtablespace" endterm="sql-createdatabase-title">
command, for example:<indexterm><primary>CREATE TABLESPACE</></>
<programlisting>
CREATE TABLESPACE fastspace LOCATION '/mnt/sda1/postgresql/data';
...
...
@@ -459,8 +460,9 @@ CREATE TABLE foo(i int);
</para>
<para>
To remove an empty tablespace, use the <xref linkend="sql-droptablespace">
command.
To remove an empty tablespace, use the <xref
linkend="sql-droptablespace" endterm="sql-droptablespace-title">
command.
</para>
<para>
...
...
doc/src/sgml/mvcc.sgml
浏览文件 @
8c05ca77
<!--
$PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.5
0 2005/04/28 21:47:09 tgl
Exp $
$PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.5
1 2005/06/13 02:40:05 neilc
Exp $
-->
<chapter id="mvcc">
...
...
@@ -224,7 +224,7 @@ $PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.50 2005/04/28 21:47:09 tgl Exp $
<para>
To set the transaction isolation level of a transaction, use the
command <xref linkend="sql-set-transaction">.
command <xref linkend="sql-set-transaction"
endterm="sql-set-transaction-title"
>.
</para>
<sect2 id="xact-read-committed">
...
...
@@ -524,7 +524,8 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
The list below shows the available lock modes and the contexts in
which they are used automatically by
<productname>PostgreSQL</productname>. You can also acquire any
of these locks explicitly with the command <xref linkend="sql-lock">.
of these locks explicitly with the command <xref
linkend="sql-lock" endterm="sql-lock-title">.
Remember that all of these lock modes are table-level locks,
even if the name contains the word
<quote>row</quote>; the names of the lock modes are historical.
...
...
doc/src/sgml/query.sgml
浏览文件 @
8c05ca77
<!--
$PostgreSQL: pgsql/doc/src/sgml/query.sgml,v 1.4
4 2005/03/10 23:21:20 tgl
Exp $
$PostgreSQL: pgsql/doc/src/sgml/query.sgml,v 1.4
5 2005/06/13 02:40:06 neilc
Exp $
-->
<chapter id="tutorial-sql">
...
...
@@ -269,7 +269,8 @@ COPY weather FROM '/home/user/weather.txt';
where the file name for the source file must be available to the
backend server machine, not the client, since the backend server
reads the file directly. You can read more about the
<command>COPY</command> command in <xref linkend="sql-copy">.
<command>COPY</command> command in <xref linkend="sql-copy"
endterm="sql-copy-title">.
</para>
</sect1>
...
...
doc/src/sgml/ref/psql-ref.sgml
浏览文件 @
8c05ca77
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.14
2 2005/06/10 16:31:48 momjian
Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.14
3 2005/06/13 02:40:08 neilc
Exp $
PostgreSQL documentation
-->
...
...
@@ -1036,9 +1036,9 @@ testdb=>
</para>
<para>
The commands <
xref linkend="SQL-GRANT"
> and
<
xref linkend="SQL-REVOKE">
are used to set access privileges. See <xref linkend="SQL-GRANT
">
The commands <
command>GRANT</command
> and
<
command>REVOKE</command> are used to set access privileges.
See <xref linkend="sql-grant" endterm="sql-grant-title
">
for more information.
</para>
</listitem>
...
...
@@ -1740,10 +1740,10 @@ lo_import 152801
</para>
<para>
The commands <
xref linkend="SQL-GRANT"
> and
<
xref linkend="SQL-REVOKE">
are used to set access privileges. See <xref linkend="SQL-GRANT">
for
more information.
The commands <
command>GRANT</command
> and
<
command>REVOKE</command> are used to set access privileges.
See <xref linkend="sql-grant" endterm="sql-grant-title"> for
more information.
</para>
<para>
...
...
doc/src/sgml/runtime.sgml
浏览文件 @
8c05ca77
<!--
$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.32
4 2005/06/09 22:35:23 momjian
Exp $
$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.32
5 2005/06/13 02:40:06 neilc
Exp $
-->
<chapter Id="runtime">
...
...
@@ -3234,8 +3234,9 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
</para>
<para>
Consult <xref linkend="mvcc"> and <xref linkend="sql-set-transaction"> for more
information.
Consult <xref linkend="mvcc"> and <xref
linkend="sql-set-transaction"
endterm="sql-set-transaction-title"> for more information.
</para>
</listitem>
</varlistentry>
...
...
@@ -3257,7 +3258,8 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
</para>
<para>
Consult <xref linkend="sql-set-transaction"> for more information.
Consult <xref linkend="sql-set-transaction"
endterm="sql-set-transaction-title"> for more information.
</para>
</listitem>
</varlistentry>
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录