<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.18 2000/07/21 00:24:37 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.19 2000/07/22 04:45:09 momjian Exp $
Postgres documentation
-->
<para>
When doing a data only dump, <application>pg_dump</application> emits queries
to disable triggers on user tables before inserting the data and queries to
- reenable them after the data has been inserted. If the restore is stopped
+ re-enable them after the data has been inserted. If the restore is stopped
in the middle, the system catalogs may be left in the wrong state.
</para>
</listitem>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.12 2000/07/21 17:58:49 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.13 2000/07/22 04:45:09 momjian Exp $
Postgres documentation
-->
is the number of shared-memory buffers that the
<application>postmaster</application>
has allocated for the backend server processes that it starts. If the
- backend is running standalone, this specifies the number of buffers to
+ backend is running stand-alone, this specifies the number of buffers to
allocate. This value defaults to 64 buffers, where each buffer is 8k bytes
(or whatever BLCKSZ is set to in config.h).
</para>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.34 2000/07/21 17:58:49 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.35 2000/07/22 04:45:09 momjian Exp $
Postgres documentation
-->
<term><envar>DBNAME</envar></term>
<listitem>
<para>
- The name of the database you are currently connected to. This is set everytime
+ The name of the database you are currently connected to. This is set every time
you connect to a database (including program startup), but can be unset.
</para>
</listitem>
<term><envar>HOST</envar></term>
<listitem>
<para>
- The database server host you are currently connected to. This is set everytime
+ The database server host you are currently connected to. This is set every time
you connect to a database (including program startup), but can be unset.
</para>
</listitem>
<listitem>
<para>
The value of the last affected oid, as returned from an <command>INSERT</command>
- or <command>lo_insert</command> commmand. This variable is only guaranteed to be
+ or <command>lo_insert</command> command. This variable is only guaranteed to be
valid until after the result of the next <acronym>SQL</acronym> command has been
displayed.
</para>
<para>
By default, if non-interactive scripts encounter an error, such as a
malformed <acronym>SQL</acronym> query or internal meta-command,
- processing continues. This has been the traditional behaviour of
+ processing continues. This has been the traditional behavior of
<application>psql</application> but it is sometimes not desirable. If this variable
is set, script processing will immediately terminate. If the script was
called from another script it will terminate in the same fashion.
If <replaceable class="parameter">digits</replaceable> starts with
<literal>0x</literal> the rest of the characters are interpreted at a
hexadecimal digit and the character with the corresponding code is
- subsituted. If the first digit is <literal>0</literal> the characters are
+ substituted. If the first digit is <literal>0</literal> the characters are
interpreted as on octal number and the corresponding character is
substituted. Otherwise a decimal number is assumed.</para>
</listitem>
(4 rows)
</programlisting>
- Notice how the int4 colums in right aligned while the text column in left aligned.
+ Notice how the int4 columns in right aligned while the text column in left aligned.
You can make this table look differently by using the <command>\pset</command>
command:
<programlisting>
<listitem>
<para>
- <application>psql</application> only works smootly with servers of the
+ <application>psql</application> only works smoothly with servers of the
same version. That does not mean other combinations will fail outright,
but subtle and not-so-subtle problems might come up.
</para>
<listitem>
<para>
Pressing Control-C during a <quote>copy in</quote> (data sent to the
- server) doesn't show the most ideal of behaviours. If you get a message
+ server) doesn't show the most ideal of behaviors. If you get a message
such as <quote>PQexec: you gotta get out of a COPY state yourself</quote>,
simply reset the connection by entering <literal>\c - -</literal>.
</para>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/reindex.sgml,v 1.1 2000/03/31 08:16:33 inoue Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/reindex.sgml,v 1.2 2000/07/22 04:45:10 momjian Exp $
Postgres documentation
-->
REINDEX
</refname>
<refpurpose>
- Recover corrupted system indexes under standalone Postgres
+ Recover corrupted system indexes under stand-alone Postgres
</refpurpose>
</refnamediv>
<refsynopsisdiv>
<term>TABLE</term>
<listitem>
<para>
- Recreate all indexes of a specfied table.
+ Recreate all indexes of a specified table.
</para>
</listitem>
</varlistentry>
<term>DATABASE</term>
<listitem>
<para>
- Recreate all system indexes of a specfied database.
+ Recreate all system indexes of a specified database.
</para>
</listitem>
</varlistentry>
<term>INDEX</term>
<listitem>
<para>
- Recreate a specfied index.
+ Recreate a specified index.
</para>
</listitem>
</varlistentry>
<para>
<command>REINDEX</command> is used to recover corrupted system indexes.
In order to run REINDEX command,Postmaster must be shutdown and
- standalone Postgres should be started instead with options -O and
+ stand-alone Postgres should be started instead with options -O and
-P(an option to ignore system indexes). Note that we couldn't rely
on system indexes for the recovery of system indexes.
</para>
projects / postgresql / commitdiff