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

Commit651a639

Browse files
committed
proof-reading
1 parentcde7dc8 commit651a639

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

42 files changed

+559
-598
lines changed

‎doc/src/sgml/array.sgml‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/array.sgml,v 1.16 2001/11/21 05:53:40 thomas Exp $ -->
1+
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/array.sgml,v 1.17 2001/11/28 20:49:09 petere Exp $ -->
22

33
<chapter id="arrays">
44
<title>Arrays</title>
@@ -68,8 +68,8 @@ SELECT name FROM sal_emp WHERE pay_by_quarter[1] &lt;&gt; pay_by_quarter[2];
6868
The array subscript numbers are written within square brackets.
6969
<productname>PostgreSQL</productname> uses the
7070
<quote>one-based</quote> numbering convention for arrays, that is,
71-
an array ofn elements starts with <literal>array[1]</literal> and
72-
ends with <literal>array[n]</literal>.
71+
an array of<replaceable>n</> elements starts with <literal>array[1]</literal> and
72+
ends with <literal>array[<replaceable>n</>]</literal>.
7373
</para>
7474

7575
<para>
@@ -232,7 +232,7 @@ SELECT * FROM sal_emp WHERE pay_by_quarter **= 10000;
232232

233233
<tip>
234234
<para>
235-
Arrays are notlists; using arrays in the manner described in the
235+
Arrays are notsets; using arrays in the manner described in the
236236
previous paragraph is often a sign of database misdesign. The
237237
array field should generally be split off into a separate table.
238238
Tables can obviously be searched easily.

‎doc/src/sgml/backup.sgml‎

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.21 2001/11/21 05:53:40 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.22 2001/11/28 20:49:09 petere Exp $
33
-->
44
<chapter id="backup">
55
<title>Backup and Restore</title>
@@ -26,7 +26,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.21 2001/11/21 05:53:40 thom
2626
<title><acronym>SQL</> Dump</title>
2727

2828
<para>
29-
The idea behindthis method is to generate a text file with SQL
29+
The idea behindthe SQL-dump method is to generate a text file with SQL
3030
commands that, when fed back to the server, will recreate the
3131
database in the same state as it was at the time of the dump.
3232
<productname>PostgreSQL</> provides the utility program
@@ -107,8 +107,8 @@ psql <replaceable class="parameter">dbname</replaceable> &lt; <replaceable class
107107
for the pg_dump command. The database <replaceable
108108
class="parameter">dbname</replaceable> will not be created by this
109109
command, you must create it yourself from template0 before executing
110-
<application>psql</> (e.g., with <userinput>createdb -T template0
111-
<replaceable class="parameter">dbname</></userinput>).
110+
<application>psql</> (e.g., with <literal>createdb -T template0
111+
<replaceable class="parameter">dbname</></literal>).
112112
<application>psql</> supports similar options to <application>pg_dump</>
113113
for controlling the database server location and the user names. See
114114
its reference page for more information.
@@ -376,15 +376,14 @@ tar -cf backup.tar /usr/local/pgsql/data
376376
change between releases of <productname>PostgreSQL</>. This does not
377377
apply to different <quote>patch levels</quote>, these always have
378378
compatible storage formats. For example, releases 7.0.1, 7.1.2, and
379-
7.2 are not compatible, whereas&version;.1 and&version;.2 are. When you
379+
7.2 are not compatible, whereas7.1.1 and7.1.2 are. When you
380380
update between compatible versions, then you can simply reuse the
381381
data area in disk by the new executables. Otherwise you need to
382382
<quote>back up</> your data and <quote>restore</> it on the new
383383
server, using <application>pg_dump</>. (There are checks in place
384384
that prevent you from doing the wrong thing, so no harm can be done
385385
by confusing these things.) The precise installation procedure is
386-
not subject of this section, the <citetitle>Installation
387-
Instructions</citetitle> carry these details.
386+
not subject of this section, these details are in <xref linkend="installation">.
388387
</para>
389388

390389
<para>

0 commit comments

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