Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit446b547

Browse files
author
Neil Conway
committed
Minor SGML improvements.
1 parent9f89498 commit446b547

File tree

4 files changed

+17
-16
lines changed

4 files changed

+17
-16
lines changed

‎doc/src/sgml/ref/alter_domain.sgml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/alter_domain.sgml,v 1.11 2003/11/29 19:51:38 pgsql Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/alter_domain.sgml,v 1.12 2004/03/23 13:21:41 neilc Exp $
33
PostgreSQL documentation
44
-->
55

@@ -139,7 +139,7 @@ ALTER DOMAIN <replaceable class="PARAMETER">name</replaceable>
139139
</varlistentry>
140140

141141
<varlistentry>
142-
<term>CASCADE</term>
142+
<term><literal>CASCADE</literal></term>
143143
<listitem>
144144
<para>
145145
Automatically drop objects that depend on the constraint.
@@ -148,7 +148,7 @@ ALTER DOMAIN <replaceable class="PARAMETER">name</replaceable>
148148
</varlistentry>
149149

150150
<varlistentry>
151-
<term>RESTRICT</term>
151+
<term><literal>RESTRICT</literal></term>
152152
<listitem>
153153
<para>
154154
Refuse to drop the constraint if there are any dependent
@@ -174,11 +174,11 @@ ALTER DOMAIN <replaceable class="PARAMETER">name</replaceable>
174174
<title>Examples</title>
175175

176176
<para>
177-
To add a NOT NULL constraint to a domain:
177+
To add a<literal>NOT NULL</literal> constraint to a domain:
178178
<programlisting>
179179
ALTER DOMAIN zipcode SET NOT NULL;
180180
</programlisting>
181-
To remove a NOT NULL constraint from a domain:
181+
To remove a<literal>NOT NULL</literal> constraint from a domain:
182182
<programlisting>
183183
ALTER DOMAIN zipcode DROP NOT NULL;
184184
</programlisting>

‎doc/src/sgml/ref/cluster.sgml

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/cluster.sgml,v 1.31 2003/11/29 19:51:38 pgsql Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/cluster.sgml,v 1.32 2004/03/23 13:21:41 neilc Exp $
33
PostgreSQL documentation
44
-->
55

@@ -129,9 +129,10 @@ CLUSTER
129129
</para>
130130

131131
<para>
132-
Because the planner records statistics about the ordering of tables, it
133-
is advisable to run <command>ANALYZE</command> on the newly clustered
134-
table. Otherwise, the planner may make poor choices of query plans.
132+
Because the planner records statistics about the ordering of
133+
tables, it is advisable to run <xref linkend="sql-analyze"
134+
endterm="sql-analyze-title"> on the newly clustered table.
135+
Otherwise, the planner may make poor choices of query plans.
135136
</para>
136137

137138
<para>
@@ -175,7 +176,7 @@ CLUSTER emp_ind ON emp;
175176
</para>
176177

177178
<para>
178-
Cluster the <literal>employees</literal>relation using the same
179+
Cluster the <literal>employees</literal>table using the same
179180
index that was used before:
180181
<programlisting>
181182
CLUSTER emp;

‎doc/src/sgml/ref/truncate.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/truncate.sgml,v 1.16 2003/11/29 19:51:39 pgsql Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/truncate.sgml,v 1.17 2004/03/23 13:21:41 neilc Exp $
33
PostgreSQL documentation
44
-->
55

@@ -60,8 +60,8 @@ TRUNCATE [ TABLE ] <replaceable class="PARAMETER">name</replaceable>
6060
</para>
6161

6262
<para>
63-
<command>TRUNCATE</> will not run any user-definedON DELETE triggers
64-
that might exist for the table.
63+
<command>TRUNCATE</> will not run any user-defined<literal>ON
64+
DELETE</literal> triggersthat might exist for the table.
6565
</para>
6666
</refsect1>
6767

‎doc/src/sgml/ref/vacuum.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.34 2003/11/29 19:51:39 pgsql Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.35 2004/03/23 13:21:41 neilc Exp $
33
PostgreSQL documentation
44
-->
55

@@ -64,14 +64,14 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">
6464
</para>
6565

6666
<para>
67-
<command>FREEZE</command> is a special-purpose option that
67+
<literal>FREEZE</literal> is a special-purpose option that
6868
causes tuples to be marked <quote>frozen</quote> as soon as possible,
6969
rather than waiting until they are quite old. If this is done when there
7070
are no other open transactions in the same database, then it is guaranteed
7171
that all tuples in the database are <quote>frozen</> and will not be
7272
subject to transaction ID wraparound problems, no matter how long the
7373
database is left unvacuumed.
74-
<command>FREEZE</command> is not recommended for routine use. Its only
74+
<literal>FREEZE</literal> is not recommended for routine use. Its only
7575
intended usage is in connection with preparation of user-defined template
7676
databases, or other databases that are completely read-only and will not
7777
receive routine maintenance <command>VACUUM</> operations.

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp