Skip to content

P
Postgres FD Implementation
Commit dccfd749 authored by Peter Eisentraut's avatar Peter Eisentraut
Browse files
Options

Refine some things to create better looking man pages.

parent e58badfb
Show whitespace changes
Inline Side-by-side
Showing with 252 additions and 238 deletions
doc/src/sgml/ref/alter_table.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.16 2000/12/20 03:19:24 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.17 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -194,7 +194,7 @@ ALTER TABLE <replaceable class="PARAMETER">table</replaceable> ...@@ -194,7 +194,7 @@ ALTER TABLE <replaceable class="PARAMETER">table</replaceable>
new column will be ignored. You can use the <literal>SET DEFAULT</literal> new column will be ignored. You can use the <literal>SET DEFAULT</literal>
form of <command>ALTER TABLE</command> to set the default later. form of <command>ALTER TABLE</command> to set the default later.
(You will also have to update the already existing rows to the (You will also have to update the already existing rows to the
new default value, using <xref linkend="sql-update-title" new default value, using <xref linkend="sql-update"
endterm="sql-update-title">.) endterm="sql-update-title">.)
</para> </para>
......
doc/src/sgml/ref/begin.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/begin.sgml,v 1.12 2000/10/07 14:16:01 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/begin.sgml,v 1.13 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -105,8 +105,8 @@ NOTICE: BEGIN: already a transaction in progress ...@@ -105,8 +105,8 @@ NOTICE: BEGIN: already a transaction in progress
<command>BEGIN</command> initiates a user transaction in chained mode, <command>BEGIN</command> initiates a user transaction in chained mode,
i.e., all user statements after <command>BEGIN</command> command will i.e., all user statements after <command>BEGIN</command> command will
be executed in a single transaction until an explicit be executed in a single transaction until an explicit
<xref linkend="sql-commit-title" endterm="sql-commit-title">, <xref linkend="sql-commit" endterm="sql-commit-title">,
<xref linkend="sql-rollback-title" endterm="sql-rollback-title">, <xref linkend="sql-rollback" endterm="sql-rollback-title">,
or execution abort. Statements in chained mode are executed much faster, or execution abort. Statements in chained mode are executed much faster,
because transaction start/commit requires significant CPU and disk because transaction start/commit requires significant CPU and disk
activity. Execution of multiple statements inside a transaction activity. Execution of multiple statements inside a transaction
...@@ -142,15 +142,15 @@ NOTICE: BEGIN: already a transaction in progress ...@@ -142,15 +142,15 @@ NOTICE: BEGIN: already a transaction in progress
Notes Notes
</title> </title>
<para> <para>
Refer to <xref linkend="sql-lock-title" endterm="sql-lock-title"> Refer to <xref linkend="sql-lock" endterm="sql-lock-title">
for further information for further information
about locking tables inside a transaction. about locking tables inside a transaction.
</para> </para>
<para> <para>
Use <xref linkend="SQL-COMMIT-TITLE" endterm="SQL-COMMIT-TITLE"> Use <xref linkend="SQL-COMMIT" endterm="SQL-COMMIT-TITLE">
or or
<xref linkend="SQL-ROLLBACK-TITLE" endterm="SQL-ROLLBACK-TITLE"> <xref linkend="SQL-ROLLBACK" endterm="SQL-ROLLBACK-TITLE">
to terminate a transaction. to terminate a transaction.
</para> </para>
</refsect2> </refsect2>
......
doc/src/sgml/ref/commit.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/commit.sgml,v 1.9 2000/01/29 16:58:27 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/commit.sgml,v 1.10 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -110,7 +110,7 @@ NOTICE: COMMIT: no transaction in progress ...@@ -110,7 +110,7 @@ NOTICE: COMMIT: no transaction in progress
</para> </para>
<para> <para>
Use <xref linkend="SQL-ROLLBACK-TITLE" endterm="SQL-ROLLBACK-TITLE"> Use <xref linkend="SQL-ROLLBACK" endterm="SQL-ROLLBACK-TITLE">
to abort a transaction. to abort a transaction.
</para> </para>
</refsect2> </refsect2>
......
doc/src/sgml/ref/create_function.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_function.sgml,v 1.20 2000/11/20 20:36:46 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_function.sgml,v 1.21 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -123,7 +123,7 @@ CREATE FUNCTION <replaceable class="parameter">name</replaceable> ( [ <replaceab ...@@ -123,7 +123,7 @@ CREATE FUNCTION <replaceable class="parameter">name</replaceable> ( [ <replaceab
or '<replaceable class="parameter">plname</replaceable>', or '<replaceable class="parameter">plname</replaceable>',
where '<replaceable class="parameter">plname</replaceable>' where '<replaceable class="parameter">plname</replaceable>'
is the name of a created procedural language. See is the name of a created procedural language. See
<xref linkend="sql-createlanguage-title" endterm="sql-createlanguage-title"> <xref linkend="sql-createlanguage" endterm="sql-createlanguage-title">
for details. for details.
</para> </para>
</listitem> </listitem>
......
doc/src/sgml/ref/create_index.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.16 2000/10/05 19:48:17 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.17 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -228,7 +228,7 @@ ERROR: Cannot create index: 'index_name' already exists. ...@@ -228,7 +228,7 @@ ERROR: Cannot create index: 'index_name' already exists.
</para> </para>
<para> <para>
Use <xref linkend="sql-dropindex-title" endterm="sql-dropindex-title"> Use <xref linkend="sql-dropindex" endterm="sql-dropindex-title">
to remove an index. to remove an index.
</para> </para>
......
doc/src/sgml/ref/create_table.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.36 2000/10/08 13:22:24 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.37 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -242,7 +242,7 @@ ERROR: DEFAULT: type mismatched ...@@ -242,7 +242,7 @@ ERROR: DEFAULT: type mismatched
Each new table or class <replaceable class="PARAMETER">table</replaceable> Each new table or class <replaceable class="PARAMETER">table</replaceable>
is automatically created as a type. Therefore, one or more instances is automatically created as a type. Therefore, one or more instances
from the class are automatically a type and can be used in from the class are automatically a type and can be used in
<xref linkend="sql-altertable-title" endterm="sql-altertable-title"> <xref linkend="sql-altertable" endterm="sql-altertable-title">
or other <command>CREATE TABLE</command> statements. or other <command>CREATE TABLE</command> statements.
</para> </para>
......
doc/src/sgml/ref/create_table_as.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.3 1999/07/22 15:09:08 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.4 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -95,7 +95,7 @@ CREATE TABLE <replaceable>table</replaceable> [ (<replaceable>column</replaceabl ...@@ -95,7 +95,7 @@ CREATE TABLE <replaceable>table</replaceable> [ (<replaceable>column</replaceabl
<command>CREATE TABLE AS</command> enables a table to be created <command>CREATE TABLE AS</command> enables a table to be created
from the contents of an existing table. from the contents of an existing table.
It is functionality equivalent to It is functionality equivalent to
<xref linkend="sql-selectinto-title" endterm="sql-selectinto-title">, <xref linkend="sql-selectinto" endterm="sql-selectinto-title">,
but with perhaps a more direct syntax. but with perhaps a more direct syntax.
</para> </para>
</refsect1> </refsect1>
......
doc/src/sgml/ref/createdb.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/createdb.sgml,v 1.15 2000/11/22 01:41:13 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/createdb.sgml,v 1.16 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -99,7 +99,7 @@ Postgres documentation ...@@ -99,7 +99,7 @@ Postgres documentation
<listitem> <listitem>
<para> <para>
Specifies the alternative database location. See also <xref Specifies the alternative database location. See also <xref
linkend="app-initlocation" endterm="app-initlocation-title">. linkend="app-initlocation">.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -139,7 +139,7 @@ Postgres documentation ...@@ -139,7 +139,7 @@ Postgres documentation
The options <literal>-h</literal>, <literal>-p</literal>, <literal>-U</literal>, The options <literal>-h</literal>, <literal>-p</literal>, <literal>-U</literal>,
<literal>-W</literal>, and <literal>-e</literal> are passed on literally to <literal>-W</literal>, and <literal>-e</literal> are passed on literally to
<xref linkend="APP-PSQL" endterm="APP-PSQL-title">. <xref linkend="app-psql">.
</para> </para>
</refsect2> </refsect2>
...@@ -177,8 +177,8 @@ Postgres documentation ...@@ -177,8 +177,8 @@ Postgres documentation
</variablelist> </variablelist>
If there is an error condition, the backend error message will be displayed. If there is an error condition, the backend error message will be displayed.
See <xref linkend="SQL-CREATEDATABASE" endterm="SQL-CREATEDATABASE-title"> See <xref linkend="SQL-CREATEDATABASE">
and <xref linkend="APP-PSQL" endterm="APP-PSQL-title"> for possibilities. and <xref linkend="APP-PSQL"> for possibilities.
</para> </para>
</refsect2> </refsect2>
</refsynopsisdiv> </refsynopsisdiv>
...@@ -197,7 +197,7 @@ Postgres documentation ...@@ -197,7 +197,7 @@ Postgres documentation
<acronym>SQL</acronym> command <acronym>SQL</acronym> command
<xref linkend="SQL-CREATEDATABASE" endterm="SQL-CREATEDATABASE-title"> via <xref linkend="SQL-CREATEDATABASE" endterm="SQL-CREATEDATABASE-title"> via
the <productname>Postgres</productname> interactive terminal the <productname>Postgres</productname> interactive terminal
<xref linkend="APP-PSQL" endterm="APP-PSQL-title">. Thus, there is nothing <xref linkend="APP-PSQL">. Thus, there is nothing
special about creating databases via this or other methods. This means special about creating databases via this or other methods. This means
that the <application>psql</application> must be found by the script and that that the <application>psql</application> must be found by the script and that
a database server is running at the targeted host. Also, any default a database server is running at the targeted host. Also, any default
......
doc/src/sgml/ref/createlang.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/createlang.sgml,v 1.14 2000/11/22 01:41:13 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/createlang.sgml,v 1.15 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -132,7 +132,7 @@ Postgres documentation ...@@ -132,7 +132,7 @@ Postgres documentation
Most error messages are self-explanatory. If not, run Most error messages are self-explanatory. If not, run
<application>createlang</application> with the <option>--echo</option> <application>createlang</application> with the <option>--echo</option>
option and see under the respective <acronym>SQL</acronym> command option and see under the respective <acronym>SQL</acronym> command
for details. Check also under <xref linkend="APP-PSQL" endterm="APP-PSQL-title"> for details. Check also under <xref linkend="APP-PSQL">
for more possibilities. for more possibilities.
</para> </para>
</refsect2> </refsect2>
...@@ -165,8 +165,7 @@ Postgres documentation ...@@ -165,8 +165,7 @@ Postgres documentation
Notes Notes
</title> </title>
<para> <para>
Use <xref linkend="app-droplang" endterm="app-droplang-title"> Use <xref linkend="app-droplang"> to remove a language.
to remove a language.
</para> </para>
</refsect1> </refsect1>
......
doc/src/sgml/ref/createuser.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/createuser.sgml,v 1.14 2000/11/22 01:41:13 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/createuser.sgml,v 1.15 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -149,7 +149,7 @@ Postgres documentation ...@@ -149,7 +149,7 @@ Postgres documentation
<para> <para>
The options <literal>-h</literal>, <literal>-p</literal>, and <literal>-e</literal>, The options <literal>-h</literal>, <literal>-p</literal>, and <literal>-e</literal>,
are passed on literally to <xref linkend="APP-PSQL" endterm="APP-PSQL-title">. The are passed on literally to <xref linkend="APP-PSQL">. The
<application>psql</application> options <literal>-U</literal> and <literal>-W</literal> <application>psql</application> options <literal>-U</literal> and <literal>-W</literal>
are available as well, but their use can be confusing in this context. are available as well, but their use can be confusing in this context.
</para> </para>
...@@ -183,7 +183,7 @@ Postgres documentation ...@@ -183,7 +183,7 @@ Postgres documentation
If there is an error condition, the backend error message will be displayed. If there is an error condition, the backend error message will be displayed.
See <xref linkend="SQL-CREATEUSER" endterm="SQL-CREATEUSER-title"> See <xref linkend="SQL-CREATEUSER" endterm="SQL-CREATEUSER-title">
and <xref linkend="APP-PSQL" endterm="APP-PSQL-title"> for possibilities. and <xref linkend="APP-PSQL"> for possibilities.
</para> </para>
</refsect2> </refsect2>
</refsynopsisdiv> </refsynopsisdiv>
...@@ -205,7 +205,7 @@ Postgres documentation ...@@ -205,7 +205,7 @@ Postgres documentation
<acronym>SQL</acronym> command <acronym>SQL</acronym> command
<xref linkend="SQL-CREATEUSER" endterm="SQL-CREATEUSER-title"> via <xref linkend="SQL-CREATEUSER" endterm="SQL-CREATEUSER-title"> via
the <productname>Postgres</productname> interactive terminal the <productname>Postgres</productname> interactive terminal
<xref linkend="APP-PSQL" endterm="APP-PSQL-title">. Thus, there is nothing <xref linkend="APP-PSQL">. Thus, there is nothing
special about creating users via this or other methods. This means special about creating users via this or other methods. This means
that the <application>psql</application> must be found by the script and that that the <application>psql</application> must be found by the script and that
a database server is running at the targeted host. Also, any default a database server is running at the targeted host. Also, any default
......
doc/src/sgml/ref/declare.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/declare.sgml,v 1.10 2000/10/05 19:48:18 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/declare.sgml,v 1.11 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -191,7 +191,7 @@ ERROR: Named portals may only be used in begin/end transaction blocks ...@@ -191,7 +191,7 @@ ERROR: Named portals may only be used in begin/end transaction blocks
can be used to retrieve can be used to retrieve
a small number of rows at a time out of a larger query. Cursors can a small number of rows at a time out of a larger query. Cursors can
return data either in text or in binary format using return data either in text or in binary format using
<xref linkend="sql-fetch-title" endterm="sql-fetch-title">. <xref linkend="sql-fetch" endterm="sql-fetch-title">.
</para> </para>
<para> <para>
...@@ -253,10 +253,10 @@ ERROR: Named portals may only be used in begin/end transaction blocks ...@@ -253,10 +253,10 @@ ERROR: Named portals may only be used in begin/end transaction blocks
<para> <para>
Cursors are only available in transactions. Use to Cursors are only available in transactions. Use to
<xref linkend="sql-begin-title" endterm="sql-begin-title">, <xref linkend="sql-begin" endterm="sql-begin-title">,
<xref linkend="sql-commit-title" endterm="sql-commit-title"> <xref linkend="sql-commit" endterm="sql-commit-title">
and and
<xref linkend="sql-rollback-title" endterm="sql-rollback-title"> <xref linkend="sql-rollback" endterm="sql-rollback-title">
to define a transaction block. to define a transaction block.
</para> </para>
......
doc/src/sgml/ref/drop_aggregate.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_aggregate.sgml,v 1.9 2000/10/23 00:46:07 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_aggregate.sgml,v 1.10 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -118,7 +118,7 @@ ERROR: RemoveAggregate: aggregate '<replaceable class="parameter">agg</replaceab ...@@ -118,7 +118,7 @@ ERROR: RemoveAggregate: aggregate '<replaceable class="parameter">agg</replaceab
<para> <para>
Use Use
<xref linkend="sql-createaggregate-title" endterm="sql-createaggregate-title"> <xref linkend="sql-createaggregate" endterm="sql-createaggregate-title">
to create aggregate functions. to create aggregate functions.
</para> </para>
</refsect2> </refsect2>
......
doc/src/sgml/ref/drop_function.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_function.sgml,v 1.8 2000/05/18 14:24:33 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_function.sgml,v 1.9 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -116,7 +116,7 @@ NOTICE RemoveFunction: Function "<replaceable class="parameter">name</replaceabl ...@@ -116,7 +116,7 @@ NOTICE RemoveFunction: Function "<replaceable class="parameter">name</replaceabl
<para> <para>
Refer to Refer to
<xref linkend="sql-createfunction-title" endterm="sql-createfunction-title"> <xref linkend="sql-createfunction" endterm="sql-createfunction-title">
for information on creating aggregate functions. for information on creating aggregate functions.
</para> </para>
......
doc/src/sgml/ref/drop_index.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_index.sgml,v 1.8 2000/10/22 23:32:38 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_index.sgml,v 1.9 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -108,7 +108,7 @@ ERROR: index "<replaceable class="PARAMETER">index_name</replaceable>" does not ...@@ -108,7 +108,7 @@ ERROR: index "<replaceable class="PARAMETER">index_name</replaceable>" does not
</para> </para>
<para> <para>
Refer to Refer to
<xref linkend="sql-createindex-title" endterm="sql-createindex-title"> <xref linkend="sql-createindex" endterm="sql-createindex-title">
for information on how to create indexes. for information on how to create indexes.
</para> </para>
</refsect2> </refsect2>
......
doc/src/sgml/ref/drop_language.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_language.sgml,v 1.8 2000/11/04 21:04:54 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_language.sgml,v 1.9 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -110,7 +110,7 @@ ERROR: Language "<replaceable class="parameter">name</replaceable>" doesn't exis ...@@ -110,7 +110,7 @@ ERROR: Language "<replaceable class="parameter">name</replaceable>" doesn't exis
</para> </para>
<para> <para>
Refer to Refer to
<xref linkend="sql-createlanguage-title" endterm="sql-createlanguage-title"> <xref linkend="sql-createlanguage" endterm="sql-createlanguage-title">
for information on how to create procedural languages. for information on how to create procedural languages.
</para> </para>
......
doc/src/sgml/ref/drop_operator.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_operator.sgml,v 1.8 2000/10/23 00:46:07 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_operator.sgml,v 1.9 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -154,7 +154,7 @@ ERROR: RemoveOperator: right unary operator '<replaceable class="PARAMETER">ope ...@@ -154,7 +154,7 @@ ERROR: RemoveOperator: right unary operator '<replaceable class="PARAMETER">ope
</para> </para>
<para> <para>
Refer to Refer to
<xref linkend="sql-createoperator-title" endterm="sql-createoperator-title"> <xref linkend="sql-createoperator" endterm="sql-createoperator-title">
for information on how to create operators. for information on how to create operators.
</para> </para>
<para> <para>
......
doc/src/sgml/ref/dropdb.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.8 2000/11/22 01:41:13 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.9 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -116,7 +116,7 @@ Postgres documentation ...@@ -116,7 +116,7 @@ Postgres documentation
The options <literal>-h</literal>, <literal>-p</literal>, <literal>-U</literal>, The options <literal>-h</literal>, <literal>-p</literal>, <literal>-U</literal>,
<literal>-W</literal>, and <literal>-e</literal> are passed on literally to <literal>-W</literal>, and <literal>-e</literal> are passed on literally to
<xref linkend="APP-PSQL" endterm="APP-PSQL-title">. <xref linkend="APP-PSQL">.
</para> </para>
</refsect2> </refsect2>
...@@ -145,7 +145,7 @@ Postgres documentation ...@@ -145,7 +145,7 @@ Postgres documentation
If there is an error condition, the backend error message will be displayed. If there is an error condition, the backend error message will be displayed.
See <xref linkend="SQL-DROPDATABASE" endterm="SQL-DROPDATABASE-title"> See <xref linkend="SQL-DROPDATABASE" endterm="SQL-DROPDATABASE-title">
and <xref linkend="APP-PSQL" endterm="APP-PSQL-title"> for possibilities. and <xref linkend="APP-PSQL"> for possibilities.
</para> </para>
</refsect2> </refsect2>
</refsynopsisdiv> </refsynopsisdiv>
...@@ -167,7 +167,7 @@ Postgres documentation ...@@ -167,7 +167,7 @@ Postgres documentation
<acronym>SQL</acronym> command <acronym>SQL</acronym> command
<xref linkend="SQL-DROPDATABASE" endterm="SQL-DROPDATABASE-title"> via <xref linkend="SQL-DROPDATABASE" endterm="SQL-DROPDATABASE-title"> via
the <productname>Postgres</productname> interactive terminal the <productname>Postgres</productname> interactive terminal
<xref linkend="APP-PSQL" endterm="APP-PSQL-title">. Thus, there is nothing <xref linkend="APP-PSQL">. Thus, there is nothing
special about dropping databases via this or other methods. This means special about dropping databases via this or other methods. This means
that the <application>psql</application> must be found by the script and that that the <application>psql</application> must be found by the script and that
a database server is running at the targeted host. Also, any default a database server is running at the targeted host. Also, any default
......
doc/src/sgml/ref/droplang.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/droplang.sgml,v 1.8 2000/11/22 01:41:13 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/droplang.sgml,v 1.9 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -132,7 +132,7 @@ Postgres documentation ...@@ -132,7 +132,7 @@ Postgres documentation
Most error messages are self-explanatory. If not, run Most error messages are self-explanatory. If not, run
<application>droplang</application> with the <option>--echo</option> <application>droplang</application> with the <option>--echo</option>
option and see under the respective <acronym>SQL</acronym> command option and see under the respective <acronym>SQL</acronym> command
for details. Check also under <xref linkend="APP-PSQL" endterm="APP-PSQL-title"> for details. Check also under <xref linkend="APP-PSQL">
for more possibilities. for more possibilities.
</para> </para>
</refsect2> </refsect2>
...@@ -166,8 +166,7 @@ Postgres documentation ...@@ -166,8 +166,7 @@ Postgres documentation
</title> </title>
<para> <para>
Use <xref linkend="app-createlang" endterm="app-createlang-title"> Use <xref linkend="app-createlang"> to add a language.
to add a language.
</para> </para>
</refsect1> </refsect1>
......
doc/src/sgml/ref/dropuser.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.9 2000/11/22 01:41:13 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.10 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -99,7 +99,7 @@ Postgres documentation ...@@ -99,7 +99,7 @@ Postgres documentation
<para> <para>
The options <literal>-h</literal>, <literal>-p</literal>, and <literal>-e</literal>, The options <literal>-h</literal>, <literal>-p</literal>, and <literal>-e</literal>,
are passed on literally to <xref linkend="APP-PSQL" endterm="APP-PSQL-title">. The are passed on literally to <xref linkend="APP-PSQL">. The
<application>psql</application> options <literal>-U</literal> and <literal>-W</literal> <application>psql</application> options <literal>-U</literal> and <literal>-W</literal>
are available as well, but they can be confusing in this context. are available as well, but they can be confusing in this context.
</para> </para>
...@@ -134,7 +134,7 @@ Postgres documentation ...@@ -134,7 +134,7 @@ Postgres documentation
If there is an error condition, the backend error message will be displayed. If there is an error condition, the backend error message will be displayed.
See <xref linkend="SQL-DROPUSER" endterm="SQL-DROPUSER-title"> See <xref linkend="SQL-DROPUSER" endterm="SQL-DROPUSER-title">
and <xref linkend="APP-PSQL" endterm="APP-PSQL-title"> for possibilities. and <xref linkend="APP-PSQL"> for possibilities.
</para> </para>
</refsect2> </refsect2>
</refsynopsisdiv> </refsynopsisdiv>
...@@ -157,7 +157,7 @@ Postgres documentation ...@@ -157,7 +157,7 @@ Postgres documentation
<acronym>SQL</acronym> command <acronym>SQL</acronym> command
<xref linkend="SQL-DROPUSER" endterm="SQL-DROPUSER-title"> via <xref linkend="SQL-DROPUSER" endterm="SQL-DROPUSER-title"> via
the <productname>Postgres</productname> interactive terminal the <productname>Postgres</productname> interactive terminal
<xref linkend="APP-PSQL" endterm="APP-PSQL-title">. Thus, there is nothing <xref linkend="APP-PSQL">. Thus, there is nothing
special about removing users via this or other methods. This means special about removing users via this or other methods. This means
that the <application>psql</application> must be found by the script and that that the <application>psql</application> must be found by the script and that
a database server is running at the targeted host. Also, any default a database server is running at the targeted host. Also, any default
......
doc/src/sgml/ref/ecpg-ref.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/ecpg-ref.sgml,v 1.5 2000/10/05 19:48:18 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/ecpg-ref.sgml,v 1.6 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -8,6 +8,7 @@ Postgres documentation ...@@ -8,6 +8,7 @@ Postgres documentation
<refentrytitle id="app-ecpg-title"> <refentrytitle id="app-ecpg-title">
<application>ecpg</application> <application>ecpg</application>
</refentrytitle> </refentrytitle>
<manvolnum>1</manvolnum>
<refmiscinfo>Application</refmiscinfo> <refmiscinfo>Application</refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>
...@@ -75,7 +76,7 @@ ecpg [ -v ] [ -t ] [ -I include-path ] [ -o outfile ] file1 [ file2 ] [ ... ] ...@@ -75,7 +76,7 @@ ecpg [ -v ] [ -t ] [ -I include-path ] [ -o outfile ] file1 [ file2 ] [ ... ]
<term>-o</term> <term>-o</term>
<listitem> <listitem>
<para> <para>
Specifies that ecpg should write all its output to outfile. Specifies that <application>ecpg</application> should write all its output to outfile.
If no such option is given the output is written to If no such option is given the output is written to
<filename><replaceable>name</replaceable>.c</filename>, <filename><replaceable>name</replaceable>.c</filename>,
assuming the input file was assuming the input file was
...@@ -115,7 +116,7 @@ ecpg [ -v ] [ -t ] [ -I include-path ] [ -o outfile ] file1 [ file2 ] [ ... ] ...@@ -115,7 +116,7 @@ ecpg [ -v ] [ -t ] [ -I include-path ] [ -o outfile ] file1 [ file2 ] [ ... ]
<term><replaceable>return value</replaceable></term> <term><replaceable>return value</replaceable></term>
<listitem> <listitem>
<para> <para>
ecpg returns 0 to the shell on successful completion, -1 <application>ecpg</application> returns 0 to the shell on successful completion, -1
for errors. for errors.
</para> </para>
</listitem> </listitem>
...@@ -135,12 +136,12 @@ ecpg [ -v ] [ -t ] [ -I include-path ] [ -o outfile ] file1 [ file2 ] [ ... ] ...@@ -135,12 +136,12 @@ ecpg [ -v ] [ -t ] [ -I include-path ] [ -o outfile ] file1 [ file2 ] [ ... ]
</para> </para>
<para> <para>
<ulink url="mailto:linus@epact.se">Linus Tolke</ulink> was the Linus Tolke (<email>linus@epact.se</email>) was the
original author of <application>ecpg</application> (up to version 0.2). original author of <application>ecpg</application> (up to version 0.2).
<ulink url="mailto:meskes@debian.org">Michael Meskes</ulink> Michael Meskes (<email>meskes@debian.org</email>)
is the current author and maintainer of <application>ecpg</application>. is the current author and maintainer of <application>ecpg</application>.
<ulink url="mailto:tomg@q8.nrnet.org">Thomas Good</ulink> Thomas Good (<email>tomg@q8.nrnet.org</email>)
is the author of the last revision of the ecpg man page, on which is the author of the last revision of the <application>ecpg</application> man page, on which
this document is based. this document is based.
</para> </para>
</refsect1> </refsect1>
...@@ -203,7 +204,7 @@ gcc -g -I /usr/local/pgsql/include [ -o <replaceable>file</replaceable> ] <repla ...@@ -203,7 +204,7 @@ gcc -g -I /usr/local/pgsql/include [ -o <replaceable>file</replaceable> ] <repla
<title>Variable Declaration</title> <title>Variable Declaration</title>
<para> <para>
Variables declared within ecpg source code must be prepended with: Variables declared within <application>ecpg</application> source code must be prepended with:
<programlisting> <programlisting>
EXEC SQL BEGIN DECLARE SECTION; EXEC SQL BEGIN DECLARE SECTION;
...@@ -247,8 +248,8 @@ EXEC SQL INCLUDE sqlca; ...@@ -247,8 +248,8 @@ EXEC SQL INCLUDE sqlca;
followed, i.e., using uppercase to separate embedded SQL followed, i.e., using uppercase to separate embedded SQL
from C statements, sqlca (which includes the sqlca.h from C statements, sqlca (which includes the sqlca.h
header file) MUST be lowercase. This is because the EXEC SQL header file) MUST be lowercase. This is because the EXEC SQL
prefix indicates that this INCLUDE will be parsed by ecpg. prefix indicates that this INCLUDE will be parsed by <application>ecpg</application>.
ecpg observes case sensitivity (SQLCA.h will not be found). <application>ecpg</application> observes case sensitivity (SQLCA.h will not be found).
<command>EXEC SQL INCLUDE</command> <command>EXEC SQL INCLUDE</command>
can be used to include other header files can be used to include other header files
as long as case sensitivity is observed. as long as case sensitivity is observed.
......
doc/src/sgml/ref/end.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/end.sgml,v 1.3 2000/03/27 17:14:43 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/end.sgml,v 1.4 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -96,7 +96,7 @@ NOTICE: COMMIT: no transaction in progress ...@@ -96,7 +96,7 @@ NOTICE: COMMIT: no transaction in progress
<para> <para>
<command>END</command> is a <productname>Postgres</productname> <command>END</command> is a <productname>Postgres</productname>
extension, and is a synonym for the SQL92-compatible extension, and is a synonym for the SQL92-compatible
<xref linkend="sql-commit-title" endterm="sql-commit-title">. <xref linkend="sql-commit" endterm="sql-commit-title">.
</para> </para>
<refsect2 id="R2-SQL-END-3"> <refsect2 id="R2-SQL-END-3">
...@@ -111,7 +111,7 @@ NOTICE: COMMIT: no transaction in progress ...@@ -111,7 +111,7 @@ NOTICE: COMMIT: no transaction in progress
</para> </para>
<para> <para>
Use <xref linkend="SQL-ROLLBACK-TITLE" endterm="SQL-ROLLBACK-TITLE"> Use <xref linkend="SQL-ROLLBACK" endterm="SQL-ROLLBACK-TITLE">
to abort a transaction. to abort a transaction.
</para> </para>
</refsect2> </refsect2>
...@@ -146,7 +146,7 @@ END WORK; ...@@ -146,7 +146,7 @@ END WORK;
<para> <para>
<command>END</command> is a <productname>PostgreSQL</productname> <command>END</command> is a <productname>PostgreSQL</productname>
extension which provides functionality equivalent to extension which provides functionality equivalent to
<xref linkend="sql-commit-title" endterm="sql-commit-title">. <xref linkend="sql-commit" endterm="sql-commit-title">.
</para> </para>
</refsect2> </refsect2>
</refsect1> </refsect1>
......
doc/src/sgml/ref/fetch.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/fetch.sgml,v 1.13 2000/10/05 19:48:18 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/fetch.sgml,v 1.14 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -272,15 +272,15 @@ FETCH RELATIVE 0 FROM <replaceable class="PARAMETER">cursor</replaceable>. ...@@ -272,15 +272,15 @@ FETCH RELATIVE 0 FROM <replaceable class="PARAMETER">cursor</replaceable>.
<para> <para>
Use Use
<xref linkend="sql-move-title" endterm="sql-move-title"> <xref linkend="sql-move" endterm="sql-move-title">
to change cursor position. to change cursor position.
<xref linkend="sql-declare-title" endterm="sql-declare-title"> <xref linkend="sql-declare" endterm="sql-declare-title">
will define a cursor. will define a cursor.
Refer to Refer to
<xref linkend="sql-begin-title" endterm="sql-begin-title">, <xref linkend="sql-begin" endterm="sql-begin-title">,
<xref linkend="sql-commit-title" endterm="sql-commit-title">, <xref linkend="sql-commit" endterm="sql-commit-title">,
and and
<xref linkend="sql-rollback-title" endterm="sql-rollback-title"> <xref linkend="sql-rollback" endterm="sql-rollback-title">
for further information about transactions. for further information about transactions.
</para> </para>
</refsect2> </refsect2>
......
doc/src/sgml/ref/initdb.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/initdb.sgml,v 1.13 2000/11/11 23:01:45 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/initdb.sgml,v 1.14 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
<refentry id="APP-INITDB"> <refentry id="APP-INITDB">
<docinfo> <docinfo>
<date>2000-11-11</date> <date>2000-12-25</date>
</docinfo> </docinfo>
<refmeta> <refmeta>
...@@ -58,7 +58,7 @@ Postgres documentation ...@@ -58,7 +58,7 @@ Postgres documentation
<para> <para>
Creating a database system consists of creating the directories in which Creating a database system consists of creating the directories in which
the database data will live, generating the shared catalog tables the database data will live, generating the shared catalog tables
(tables that don't belong to any particular database), and (tables that do not belong to any particular database), and
creating the <literal>template1</literal> creating the <literal>template1</literal>
database. When you create a new database, everything in the database. When you create a new database, everything in the
<literal>template1</literal> database is copied. <literal>template1</literal> database is copied.
...@@ -94,11 +94,13 @@ Postgres documentation ...@@ -94,11 +94,13 @@ Postgres documentation
<term>-D <replaceable class="parameter">dbdir</replaceable></term> <term>-D <replaceable class="parameter">dbdir</replaceable></term>
<listitem> <listitem>
<para> <para>
This option specifies where in the file system the database should be This option specifies where in the file system the database
stored. This is the only information required by initdb, but you can avoid should be stored. This is the only information required by
it by setting the <envar>PGDATA</envar> environment variable, which <application>initdb</application>, but you can avoid it by
can be convenient since the database server (<filename>postmaster</filename>) setting the <envar>PGDATA</envar> environment variable, which
can find the database directory later by the same variable. can be convenient since the database server
(<filename>postmaster</filename>) can find the database
directory later by the same variable.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -108,10 +110,11 @@ Postgres documentation ...@@ -108,10 +110,11 @@ Postgres documentation
<term>-i <replaceable class="parameter">sysid</replaceable></term> <term>-i <replaceable class="parameter">sysid</replaceable></term>
<listitem> <listitem>
<para> <para>
Selects the system id of the database superuser. This defaults to Selects the system id of the database superuser. This defaults
the effective user id of the user running initdb. It is really to the effective user id of the user running
not important what the superuser's sysid is, but one might choose <application>initdb</application>. It is really not important
to start the numbering at some number like 1. what the superuser's sysid is, but one might choose to start
the numbering at some number like 1.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -121,10 +124,11 @@ Postgres documentation ...@@ -121,10 +124,11 @@ Postgres documentation
<term>-W</term> <term>-W</term>
<listitem> <listitem>
<para> <para>
Makes initdb prompt for a password of the database superuser. If you Makes <application>initdb</application> prompt for a password
don't plan on using password authentication, this is not important. of the database superuser. If you don't plan on using password
Otherwise you won't be able to use password authentication until authentication, this is not important. Otherwise you won't be
you have a password set up. able to use password authentication until you have a password
set up.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -154,10 +158,10 @@ Postgres documentation ...@@ -154,10 +158,10 @@ Postgres documentation
<term>-L <replaceable class="parameter">directory</replaceable></term> <term>-L <replaceable class="parameter">directory</replaceable></term>
<listitem> <listitem>
<para> <para>
Specifies where initdb should find its input files to Specifies where <application>initdb</application> should find
initialize the database system. This is normally not its input files to initialize the database system. This is
necessary. You will be told if you need to specify their normally not necessary. You will be told if you need to
location explicitly. specify their location explicitly.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
......
doc/src/sgml/ref/insert.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/insert.sgml,v 1.11 2000/10/20 14:02:12 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/insert.sgml,v 1.12 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -227,7 +227,7 @@ INSERT INTO tictactoe (game, board) ...@@ -227,7 +227,7 @@ INSERT INTO tictactoe (game, board)
Possible limitations in features of the Possible limitations in features of the
<replaceable class="PARAMETER">query</replaceable> <replaceable class="PARAMETER">query</replaceable>
clause are documented for clause are documented for
<xref linkend="sql-select-title" endterm="sql-select-title">. <xref linkend="sql-select" endterm="sql-select-title">.
</para> </para>
</refsect2> </refsect2>
</refsect1> </refsect1>
......
doc/src/sgml/ref/listen.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/listen.sgml,v 1.8 2000/03/26 18:32:27 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/listen.sgml,v 1.9 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -128,7 +128,7 @@ NOTICE Async_Listen: We are already listening on <replaceable class="PARAMETER"> ...@@ -128,7 +128,7 @@ NOTICE Async_Listen: We are already listening on <replaceable class="PARAMETER">
</para> </para>
<para> <para>
<xref linkend="sql-notify-title" endterm="sql-notify-title"> <xref linkend="sql-notify" endterm="sql-notify-title">
contains a more extensive contains a more extensive
discussion of the use of <command>LISTEN</command> and discussion of the use of <command>LISTEN</command> and
<command>NOTIFY</command>. <command>NOTIFY</command>.
......
doc/src/sgml/ref/lock.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/lock.sgml,v 1.22 2000/10/05 19:48:18 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/lock.sgml,v 1.23 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -434,7 +434,7 @@ COMMIT WORK; ...@@ -434,7 +434,7 @@ COMMIT WORK;
There is no <command>LOCK TABLE</command> in <acronym>SQL92</acronym>, There is no <command>LOCK TABLE</command> in <acronym>SQL92</acronym>,
which instead uses <command>SET TRANSACTION</command> to specify which instead uses <command>SET TRANSACTION</command> to specify
concurrency levels on transactions. We support that too; see concurrency levels on transactions. We support that too; see
<xref linkend="SQL-SET-TITLE" endterm="SQL-SET-TITLE"> for details. <xref linkend="SQL-SET-TRANSACTION" endterm="SQL-SET-TRANSACTION-TITLE"> for details.
</para> </para>
</refsect2> </refsect2>
</refsect1> </refsect1>
......
doc/src/sgml/ref/move.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/move.sgml,v 1.9 2000/05/11 17:32:33 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/move.sgml,v 1.10 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -44,7 +44,7 @@ MOVE [ <replaceable class="PARAMETER">direction</replaceable> ] [ <replaceable c ...@@ -44,7 +44,7 @@ MOVE [ <replaceable class="PARAMETER">direction</replaceable> ] [ <replaceable c
</para> </para>
<para> <para>
Refer to Refer to
<xref linkend="sql-fetch-title" endterm="sql-fetch-title"> <xref linkend="sql-fetch" endterm="sql-fetch-title">
for details on syntax and usage. for details on syntax and usage.
</para> </para>
...@@ -63,16 +63,16 @@ MOVE [ <replaceable class="PARAMETER">direction</replaceable> ] [ <replaceable c ...@@ -63,16 +63,16 @@ MOVE [ <replaceable class="PARAMETER">direction</replaceable> ] [ <replaceable c
<para> <para>
Refer to Refer to
<xref linkend="sql-fetch-title" endterm="sql-fetch-title"> <xref linkend="sql-fetch" endterm="sql-fetch-title">
for a description of valid arguments. for a description of valid arguments.
Refer to Refer to
<xref linkend="sql-declare-title" endterm="sql-declare-title"> <xref linkend="sql-declare" endterm="sql-declare-title">
to define a cursor. to define a cursor.
Refer to Refer to
<xref linkend="sql-begin-title" endterm="sql-begin-title">, <xref linkend="sql-begin" endterm="sql-begin-title">,
<xref linkend="sql-commit-title" endterm="sql-commit-title">, <xref linkend="sql-commit" endterm="sql-commit-title">,
and and
<xref linkend="sql-rollback-title" endterm="sql-rollback-title"> <xref linkend="sql-rollback" endterm="sql-rollback-title">
for further information about transactions. for further information about transactions.
</para> </para>
</refsect2> </refsect2>
......
doc/src/sgml/ref/pg_ctl-ref.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml,v 1.4 2000/11/25 17:17:30 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml,v 1.5 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -64,9 +64,8 @@ Postgres documentation ...@@ -64,9 +64,8 @@ Postgres documentation
<title>Description</title> <title>Description</title>
<para> <para>
<application>pg_ctl</application> is a utility for starting, <application>pg_ctl</application> is a utility for starting,
stopping, or restarting the <xref linkend="app-postmaster" stopping, or restarting the <xref linkend="app-postmaster">, or
endterm="app-postmaster-title">, or displaying the status of a displaying the status of a running postmaster.
running postmaster.
</para> </para>
<refsect2 id="app-pg-ctl-options"> <refsect2 id="app-pg-ctl-options">
......
doc/src/sgml/ref/pg_dump.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.26 2000/11/30 23:20:50 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.27 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
<refentry id="APP-PGDUMP"> <refentry id="APP-PGDUMP">
<docinfo>
<date>2000-12-25</date>
</docinfo>
<refmeta> <refmeta>
<refentrytitle id="app-pgdump-title"> <refentrytitle id="app-pgdump-title">
<application>pg_dump</application> <application>pg_dump</application>
</refentrytitle> </refentrytitle>
<manvolnum>1</manvolnum>
<refmiscinfo>Application</refmiscinfo> <refmiscinfo>Application</refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>
...@@ -443,7 +448,7 @@ dumpSequence(<replaceable class="parameter">table</replaceable>): SELECT failed ...@@ -443,7 +448,7 @@ dumpSequence(<replaceable class="parameter">table</replaceable>): SELECT failed
and other architectures. and other architectures.
</para> </para>
<para> <para>
The archive files, new with this v7.1, contain enough information for The archive files, new with version 7.1, contain enough information for
<APPLICATION>pg_restore</APPLICATION> to rebuild the database, but also <APPLICATION>pg_restore</APPLICATION> to rebuild the database, but also
allow pg_restore to be selective about what is restored, or even to allow pg_restore to be selective about what is restored, or even to
reorder the items prior to being restored. The archive files should reorder the items prior to being restored. The archive files should
......
doc/src/sgml/ref/pg_dumpall.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.17 2000/12/19 22:12:46 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.18 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -36,9 +36,9 @@ Postgres documentation ...@@ -36,9 +36,9 @@ Postgres documentation
<application>pg_dumpall</application> is a utility for writing out <application>pg_dumpall</application> is a utility for writing out
(<quote>dumping</quote>) all Postgres databases of a cluster into (<quote>dumping</quote>) all Postgres databases of a cluster into
one script file. The script file contains SQL commands that can be one script file. The script file contains SQL commands that can be
used as input to <xref linkend="app-psql" endterm="app-psql-title"> used as input to <xref linkend="app-psql">
to restore the databases. It does this by calling <xref to restore the databases. It does this by calling <xref
linkend="app-pgdump" endterm="app-pgdump-title"> for each database linkend="app-pgdump"> for each database
in a cluster. <application>pg_dumpall</application> also dumps in a cluster. <application>pg_dumpall</application> also dumps
global objects that are common to all databases. global objects that are common to all databases.
(<application>pg_dump</application> does not save these objects.) (<application>pg_dump</application> does not save these objects.)
...@@ -110,7 +110,7 @@ Postgres documentation ...@@ -110,7 +110,7 @@ Postgres documentation
<para> <para>
Any other command line parameters are passed to the underlying Any other command line parameters are passed to the underlying
<xref endterm="app-pgdump-title" linkend="app-pgdump-title"> <xref linkend="app-pgdump">
calls. This is useful to control some aspects of the output calls. This is useful to control some aspects of the output
format, but some options such as <option>-f</option>, format, but some options such as <option>-f</option>,
<option>-t</option>, and <replaceable <option>-t</option>, and <replaceable
...@@ -145,9 +145,8 @@ Postgres documentation ...@@ -145,9 +145,8 @@ Postgres documentation
<title>See Also</title> <title>See Also</title>
<para> <para>
<xref linkend="app-pgdump" endterm="app-pgdump-title">, <xref <xref linkend="app-pgdump">, <xref linkend="app-psql">. Check
linkend="app-psql" endterm="app-psql-title">. Check there for there for details on possible error conditions.
details on possible error conditions.
</para> </para>
</refsect1> </refsect1>
......
doc/src/sgml/ref/pg_passwd.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_passwd.sgml,v 1.4 2000/11/18 19:05:58 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_passwd.sgml,v 1.5 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -49,7 +49,7 @@ Postgres documentation ...@@ -49,7 +49,7 @@ Postgres documentation
</para> </para>
<para> <para>
Supply the name of the password file as argument to the pg_passwd Supply the name of the password file as argument to the <application>pg_passwd</application>
command. To be of use for client authentication the file needs to command. To be of use for client authentication the file needs to
be location in the server's data directory, and the base name of be location in the server's data directory, and the base name of
the file needs to be specified in the the file needs to be specified in the
...@@ -88,7 +88,7 @@ host unv 133.65.96.250 255.255.255.255 password passwords ...@@ -88,7 +88,7 @@ host unv 133.65.96.250 255.255.255.255 password passwords
<note> <note>
<para> <para>
It is also useful to have entries in password file with an empty It is also useful to have entries in a password file with an empty
password field. (This is different from an empty password.) password field. (This is different from an empty password.)
These entries cannot be managed by These entries cannot be managed by
<application>pg_passwd</application>, but it is always possible to <application>pg_passwd</application>, but it is always possible to
......
doc/src/sgml/ref/pg_restore.sgml
View file @ dccfd749
...@@ -3,6 +3,7 @@ ...@@ -3,6 +3,7 @@
<refentrytitle id="app-pgrestore-title"> <refentrytitle id="app-pgrestore-title">
<application>pg_restore</application> <application>pg_restore</application>
</refentrytitle> </refentrytitle>
<manvolnum>1</manvolnum>
<refmiscinfo>Application</refmiscinfo> <refmiscinfo>Application</refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>
......
doc/src/sgml/ref/pg_upgrade.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_upgrade.sgml,v 1.11 2000/07/22 02:39:10 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pg_upgrade.sgml,v 1.12 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -8,6 +8,7 @@ Postgres documentation ...@@ -8,6 +8,7 @@ Postgres documentation
<refentrytitle id="APP-PG-UPGRADE-TITLE"> <refentrytitle id="APP-PG-UPGRADE-TITLE">
<application>pg_upgrade</application> <application>pg_upgrade</application>
</refentrytitle> </refentrytitle>
<manvolnum>1</manvolnum>
<refmiscinfo>Application</refmiscinfo> <refmiscinfo>Application</refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>
......
doc/src/sgml/ref/pgaccess-ref.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgaccess-ref.sgml,v 1.5 2000/10/05 19:48:18 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgaccess-ref.sgml,v 1.6 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -8,6 +8,7 @@ Postgres documentation ...@@ -8,6 +8,7 @@ Postgres documentation
<refentrytitle id="app-pgaccess-title"> <refentrytitle id="app-pgaccess-title">
<application>pgaccess</application> <application>pgaccess</application>
</refentrytitle> </refentrytitle>
<manvolnum>1</manvolnum>
<refmiscinfo>Application</refmiscinfo> <refmiscinfo>Application</refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>
...@@ -69,9 +70,9 @@ pgaccess [ <replaceable class="parameter">dbname</replaceable> ] ...@@ -69,9 +70,9 @@ pgaccess [ <replaceable class="parameter">dbname</replaceable> ]
<para> <para>
Another way of accessing <productname>Postgres</productname> Another way of accessing <productname>Postgres</productname>
through tcl is to use through tcl is to use
<xref linkend="app-pgtclsh" endterm="app-pgtclsh-title"> <xref linkend="app-pgtclsh">
or or
<xref linkend="app-pgtksh" endterm="app-pgtksh-title">. <xref linkend="app-pgtksh">.
</para> </para>
<para> <para>
......
doc/src/sgml/ref/pgadmin-ref.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgadmin-ref.sgml,v 1.6 2000/03/27 17:14:43 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgadmin-ref.sgml,v 1.7 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -8,6 +8,7 @@ Postgres documentation ...@@ -8,6 +8,7 @@ Postgres documentation
<refentrytitle id="app-pgadmin-title"> <refentrytitle id="app-pgadmin-title">
<application>pgadmin</application> <application>pgadmin</application>
</refentrytitle> </refentrytitle>
<manvolnum>1</manvolnum>
<refmiscinfo>Application</refmiscinfo> <refmiscinfo>Application</refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>
......
doc/src/sgml/ref/pgtclsh.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgtclsh.sgml,v 1.1 1999/08/06 13:50:31 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgtclsh.sgml,v 1.2 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
<refentry id="APP-PGTCLSH"> <refentry id="APP-PGTCLSH">
<docinfo>
<date>2000-12-25</date>
</docinfo>
<refmeta> <refmeta>
<refentrytitle id="app-pgtclsh-title"> <refentrytitle id="app-pgtclsh-title">
<application>pgtclsh</application> <application>pgtclsh</application>
</refentrytitle> </refentrytitle>
<manvolnum>1</manvolnum>
<refmiscinfo>Application</refmiscinfo> <refmiscinfo>Application</refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>
...@@ -19,12 +24,9 @@ Postgres documentation ...@@ -19,12 +24,9 @@ Postgres documentation
</refpurpose> </refpurpose>
</refnamediv> </refnamediv>
<refsynopsisdiv> <refsynopsisdiv>
<refsynopsisdivinfo> <cmdsynopsis>
<date>1999-08-03</date> <command>pgtclsh</command>
</refsynopsisdivinfo> </cmdsynopsis>
<synopsis>
pgtclsh [ <replaceable class="parameter">dbname</replaceable> ]
</synopsis>
<refsect2 id="R2-APP-PGTCLSH-1"> <refsect2 id="R2-APP-PGTCLSH-1">
<title> <title>
...@@ -66,9 +68,9 @@ pgtclsh [ <replaceable class="parameter">dbname</replaceable> ] ...@@ -66,9 +68,9 @@ pgtclsh [ <replaceable class="parameter">dbname</replaceable> ]
<para> <para>
Another way of accessing <productname>Postgres</productname> Another way of accessing <productname>Postgres</productname>
through tcl is to use through tcl is to use
<xref linkend="app-pgtksh" endterm="app-pgtksh-title"> <xref linkend="app-pgtksh">
or or
<xref linkend="app-pgaccess" endterm="app-pgaccess-title">. <xref linkend="app-pgaccess">.
</para> </para>
</refsect1> </refsect1>
</refentry> </refentry>
......
doc/src/sgml/ref/pgtksh.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgtksh.sgml,v 1.1 1999/08/06 13:50:31 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgtksh.sgml,v 1.2 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
<refentry id="APP-PGTKSH"> <refentry id="APP-PGTKSH">
<docinfo>
<date>2000-12-25</date>
</docinfo>
<refmeta> <refmeta>
<refentrytitle id="app-pgtksh-title"> <refentrytitle id="app-pgtksh-title">
<application>pgtksh</application> <application>pgtksh</application>
</refentrytitle> </refentrytitle>
<manvolnum>1</manvolnum>
<refmiscinfo>Application</refmiscinfo> <refmiscinfo>Application</refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>
...@@ -19,12 +24,9 @@ Postgres documentation ...@@ -19,12 +24,9 @@ Postgres documentation
</refpurpose> </refpurpose>
</refnamediv> </refnamediv>
<refsynopsisdiv> <refsynopsisdiv>
<refsynopsisdivinfo> <cmdsynopsis>
<date>1999-08-03</date> <command>pgtksh</command>
</refsynopsisdivinfo> </cmdsynopsis>
<synopsis>
pgtksh [ <replaceable class="parameter">dbname</replaceable> ]
</synopsis>
<refsect2 id="R2-APP-PGTKSH-1"> <refsect2 id="R2-APP-PGTKSH-1">
<title> <title>
...@@ -66,9 +68,9 @@ pgtksh [ <replaceable class="parameter">dbname</replaceable> ] ...@@ -66,9 +68,9 @@ pgtksh [ <replaceable class="parameter">dbname</replaceable> ]
<para> <para>
Another way of accessing <productname>Postgres</productname> Another way of accessing <productname>Postgres</productname>
through <acronym>TCL</acronym> is to use through <acronym>TCL</acronym> is to use
<xref linkend="app-pgtclsh" endterm="app-pgtclsh-title"> <xref linkend="app-pgtclsh">
or or
<xref linkend="app-pgaccess" endterm="app-pgaccess-title">. <xref linkend="app-pgaccess">.
</para> </para>
</refsect1> </refsect1>
</refentry> </refentry>
......
doc/src/sgml/ref/postgres-ref.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.15 2000/11/14 18:11:31 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.16 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -80,13 +80,12 @@ Postgres documentation ...@@ -80,13 +80,12 @@ Postgres documentation
<productname>PostgreSQL</productname> server process that processes <productname>PostgreSQL</productname> server process that processes
queries. The second form above is how queries. The second form above is how
<application>postgres</application> is invoked by the <xref <application>postgres</application> is invoked by the <xref
linkend="app-postmaster" endterm="app-postmaster-title"> (only linkend="app-postmaster"> (only
conceptually, since both <filename>postmaster</filename> and conceptually, since both <filename>postmaster</filename> and
<filename>postgres</filename> are in fact the same program); it <filename>postgres</filename> are in fact the same program); it
should not be invoked directly this way. The first form invokes should not be invoked directly this way. The first form invokes
the server directly in interactive mode. The primary use for this the server directly in interactive mode. The primary use for this
mode is for bootstrapping by <xref linkend="app-initdb" mode is for bootstrapping by <xref linkend="app-initdb">.
endterm="app-initdb-title">.
</para> </para>
<para> <para>
...@@ -109,7 +108,7 @@ Postgres documentation ...@@ -109,7 +108,7 @@ Postgres documentation
<para> <para>
When <application>postgres</application> is started by a <xref When <application>postgres</application> is started by a <xref
linkend="app-postmaster" endterm="app-postmaster-title"> then it linkend="app-postmaster"> then it
inherits all options set by the latter. Additionally, inherits all options set by the latter. Additionally,
<application>postgres</application>-specific options can be passed <application>postgres</application>-specific options can be passed
from the <application>postmaster</application> with the from the <application>postmaster</application> with the
...@@ -134,7 +133,7 @@ Postgres documentation ...@@ -134,7 +133,7 @@ Postgres documentation
The options <option>-A</option>, <option>-B</option>, The options <option>-A</option>, <option>-B</option>,
<option>-c</option>, <option>-d</option>, <option>-D</option>, <option>-c</option>, <option>-d</option>, <option>-D</option>,
and <option>-F</option> have the same meaning as with the <xref and <option>-F</option> have the same meaning as with the <xref
linkend="app-postmaster" endterm="app-postmaster-title">. linkend="app-postmaster">.
</para> </para>
<variablelist> <variablelist>
...@@ -358,9 +357,9 @@ Postgres documentation ...@@ -358,9 +357,9 @@ Postgres documentation
<title>See also</title> <title>See also</title>
<para> <para>
<xref linkend="app-initdb" endterm="app-initdb-title">, <xref linkend="app-initdb">,
<xref linkend="app-ipcclean" endterm="app-ipcclean-title">, <xref linkend="app-ipcclean">,
<xref linkend="app-postmaster" endterm="app-postmaster-title"> <xref linkend="app-postmaster">
</para> </para>
</refsect1> </refsect1>
......
doc/src/sgml/ref/postmaster.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.18 2000/11/30 23:20:50 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.19 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
<refentry id="APP-POSTMASTER"> <refentry id="app-postmaster">
<docinfo> <docinfo>
<date>2000-11-30</date> <date>2000-12-25</date>
</docinfo> </docinfo>
<refmeta> <refmeta>
...@@ -50,31 +50,30 @@ Postgres documentation ...@@ -50,31 +50,30 @@ Postgres documentation
(over a network or locally) to a running (over a network or locally) to a running
<application>postmaster</application>. The <application>postmaster</application>. The
<application>postmaster</application> then starts a separate server <application>postmaster</application> then starts a separate server
process (<quote><xref linkend="app-postgres" process (<quote><xref linkend="app-postgres"></quote>) to handle
endterm="app-postgres-title"></quote>) to handle the connection. the connection. The <application>postmaster</application> also
The postmaster also manages the communication among server manages the communication among server processes.
processes.
</para> </para>
<para> <para>
By default the postmaster starts in the foreground and prints log By default the <application>postmaster</application> starts in the
messages to the standard output. In practical applications the foreground and prints log messages to the standard output. In
postmaster should be started as a background process, perhaps at practical applications the <application>postmaster</application>
boot time. should be started as a background process, perhaps at boot time.
</para> </para>
<para> <para>
One postmaster always manages the data from exactly one database One <application>postmaster</application> always manages the data
cluster. A database cluster is a collection of databases that is from exactly one database cluster. A database cluster is a
stored at a common file system location. When the postmaster collection of databases that is stored at a common file system
starts it needs to know the location of the database cluster files location. When the postmaster starts it needs to know the location
(<quote>data area</quote>). This is done with the of the database cluster files (<quote>data area</quote>). This is
<option>-D</option> invocation option or the <envar>PGDATA</envar> done with the <option>-D</option> invocation option or the
environment variable; there is no default. More than one <envar>PGDATA</envar> environment variable; there is no default.
postmaster process can run on a system at one time, as long as they More than one postmaster process can run on a system at one time,
use different data areas and different communication ports (see below). as long as they use different data areas and different
A data area is created with <xref linkend="app-initdb" communication ports (see below). A data area is created with <xref
endterm="app-initdb-title">. linkend="app-initdb">.
</para> </para>
<refsect2 id="app-postmaster-options"> <refsect2 id="app-postmaster-options">
...@@ -183,7 +182,7 @@ Postgres documentation ...@@ -183,7 +182,7 @@ Postgres documentation
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term>-k <replaceable class="parameter">directoryname</replaceable></term> <term>-k <replaceable class="parameter">directory</replaceable></term>
<listitem> <listitem>
<para> <para>
Specifies the directory of the Unix-domain socket on which the Specifies the directory of the Unix-domain socket on which the
...@@ -210,10 +209,11 @@ Postgres documentation ...@@ -210,10 +209,11 @@ Postgres documentation
<listitem> <listitem>
<para> <para>
Sets the maximum number of client connections that this Sets the maximum number of client connections that this
postmaster will accept. By default, this value is 32, but it <application>postmaster</application> will accept. By
can be set as high as 1024 if your system will support that default, this value is 32, but it can be set as high as 1024
many processes. (Note that <option>-B</option> is required to if your system will support that many processes. (Note that
be at least twice <option>-N</option>.) <option>-B</option> is required to be at least twice
<option>-N</option>.)
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -223,12 +223,11 @@ Postgres documentation ...@@ -223,12 +223,11 @@ Postgres documentation
<listitem> <listitem>
<para> <para>
The command line-style options specified in <replaceable The command line-style options specified in <replaceable
class="parameter">EXTRA-OPTIONS</replaceable> are passed to class="parameter">extra-options</replaceable> are passed to
all backend server processes started by this all backend server processes started by this
<application>postmaster</application>. See <xref <application>postmaster</application>. See <xref
linkend="app-postgres" endterm="app-postgres-title"> for linkend="app-postgres"> for possibilities. If the option
possibilities. If the option string contains any spaces, the string contains any spaces, the entire string must be quoted.
entire string must be quoted.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -264,7 +263,7 @@ Postgres documentation ...@@ -264,7 +263,7 @@ Postgres documentation
Using this switch discards all logging output, which is Using this switch discards all logging output, which is
probably not what you want, since it makes it very difficult probably not what you want, since it makes it very difficult
to troubleshoot problems. See below for a better way to start to troubleshoot problems. See below for a better way to start
the postmaster in the background. the <application>postmaster</application> in the background.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -367,14 +366,14 @@ StreamServerPort: cannot bind to port ...@@ -367,14 +366,14 @@ StreamServerPort: cannot bind to port
other <application>postmaster</application> other <application>postmaster</application>
process already running on the same port number. The easiest way to process already running on the same port number. The easiest way to
determine this is by using the command determine this is by using the command
<programlisting> <screen>
$ ps -ax | grep postmaster <prompt>$</prompt> <userinput>ps ax | grep postmaster</userinput>
</programlisting> </screen>
on BSD-based systems, or or
<programlisting> <screen>
$ ps -e | grep postmast <prompt>$</prompt> <userinput>ps -e | grep postmaster</userinput>
</programlisting> </screen>
for System V-like or POSIX-compliant systems such as HP-UX. depending on your system.
</para> </para>
<para> <para>
...@@ -414,9 +413,9 @@ $ ps -e | grep postmast ...@@ -414,9 +413,9 @@ $ ps -e | grep postmast
</para> </para>
<para> <para>
To terminate the postmaster normally, the signals To terminate the <application>postmaster</application> normally,
<literal>SIGTERM</literal>, <literal>SIGINT</literal>, or the signals <literal>SIGTERM</literal>, <literal>SIGINT</literal>,
<literal>SIGQUIT</literal> can be used. The first will wait for or <literal>SIGQUIT</literal> can be used. The first will wait for
all clients to terminate before quitting, the second will all clients to terminate before quitting, the second will
forcefully disconnect all clients, and the third will quit forcefully disconnect all clients, and the third will quit
immediately without lengthy shutdown, resulting in a recovery run immediately without lengthy shutdown, resulting in a recovery run
...@@ -425,7 +424,8 @@ $ ps -e | grep postmast ...@@ -425,7 +424,8 @@ $ ps -e | grep postmast
<para> <para>
The utility command <xref linkend="app-pg-ctl"> can be used to The utility command <xref linkend="app-pg-ctl"> can be used to
start and shut down the postmaster safely and comfortably. start and shut down the <application>postmaster</application>
safely and comfortably.
</para> </para>
</refsect1> </refsect1>
......
doc/src/sgml/ref/psql-ref.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.44 2000/11/22 01:41:13 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.45 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
<refentry id="APP-PSQL"> <refentry id="APP-PSQL">
<docinfo>
<date>2000-12-25</date>
</docinfo>
<refmeta> <refmeta>
<refentrytitle id="app-psql-title"> <refentrytitle id="app-psql-title"><application>psql</application></refentrytitle>
<application>psql</application> <manvolnum>1</manvolnum>
</refentrytitle>
<refmiscinfo>Application</refmiscinfo> <refmiscinfo>Application</refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>
<refname> <refname><application>psql</application></refname>
<application>psql</application>
</refname>
<refpurpose> <refpurpose>
<productname>Postgres</productname> interactive terminal <productname>Postgres</productname> interactive terminal
</refpurpose> </refpurpose>
......
doc/src/sgml/ref/reset.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/reset.sgml,v 1.9 2000/06/18 21:24:51 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/reset.sgml,v 1.10 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -26,7 +26,7 @@ RESET <replaceable class="PARAMETER">variable</replaceable> ...@@ -26,7 +26,7 @@ RESET <replaceable class="PARAMETER">variable</replaceable>
<listitem> <listitem>
<para> <para>
The name of a run-time parameter. See <xref The name of a run-time parameter. See <xref
linkend="sql-set-title" endterm="sql-set-title"> for a list. linkend="sql-set" endterm="sql-set-title"> for a list.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -41,7 +41,7 @@ RESET <replaceable class="PARAMETER">variable</replaceable> ...@@ -41,7 +41,7 @@ RESET <replaceable class="PARAMETER">variable</replaceable>
<para> <para>
<command>RESET</command> restores run-time parameters to their <command>RESET</command> restores run-time parameters to their
default values. Refer to default values. Refer to
<xref linkend="sql-set-title" endterm="sql-set-title"> <xref linkend="sql-set" endterm="sql-set-title">
for details. <command>RESET</command> is an alternate form for for details. <command>RESET</command> is an alternate form for
<synopsis> <synopsis>
...@@ -53,7 +53,7 @@ SET <replaceable class="parameter">variable</replaceable> TO DEFAULT ...@@ -53,7 +53,7 @@ SET <replaceable class="parameter">variable</replaceable> TO DEFAULT
<refsect1> <refsect1>
<title>Diagnostics</title> <title>Diagnostics</title>
<para> <para>
See under the <xref linkend="sql-set-title" See under the <xref linkend="sql-set"
endterm="sql-set-title"> command. endterm="sql-set-title"> command.
</para> </para>
</refsect1> </refsect1>
......
doc/src/sgml/ref/revoke.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/revoke.sgml,v 1.12 2000/10/12 21:23:34 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/revoke.sgml,v 1.13 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -90,7 +90,7 @@ REVOKE <replaceable class="PARAMETER">privilege</replaceable> [, ...] ...@@ -90,7 +90,7 @@ REVOKE <replaceable class="PARAMETER">privilege</replaceable> [, ...]
<para> <para>
Privilege to define rules on table/view. Privilege to define rules on table/view.
(See (See
<xref linkend="sql-createrule-title" endterm="sql-createrule-title">). <xref linkend="sql-createrule" endterm="sql-createrule-title">).
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
...@@ -319,7 +319,7 @@ REVOKE { INSERT | UPDATE | REFERENCES } [, ...] [ ( <replaceable class="paramete ...@@ -319,7 +319,7 @@ REVOKE { INSERT | UPDATE | REFERENCES } [, ...] [ ( <replaceable class="paramete
<listitem> <listitem>
<para> <para>
Refer to Refer to
<xref linkend="sql-grant-title" endterm="sql-grant-title"> <xref linkend="sql-grant" endterm="sql-grant-title">
for details on individual fields. for details on individual fields.
</para> </para>
</listitem> </listitem>
...@@ -338,7 +338,7 @@ REVOKE GRANT OPTION FOR <replaceable class="parameter">privilege</replaceable> [ ...@@ -338,7 +338,7 @@ REVOKE GRANT OPTION FOR <replaceable class="parameter">privilege</replaceable> [
Rescinds authority for a user to grant the specified privilege Rescinds authority for a user to grant the specified privilege
to others. to others.
Refer to Refer to
<xref linkend="sql-grant-title" endterm="sql-grant-title"> <xref linkend="sql-grant" endterm="sql-grant-title">
for details on individual fields. for details on individual fields.
</para> </para>
</listitem> </listitem>
......
doc/src/sgml/ref/rollback.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/rollback.sgml,v 1.7 2000/01/29 16:58:27 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/rollback.sgml,v 1.8 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -95,9 +95,9 @@ NOTICE: ROLLBACK: no transaction in progress ...@@ -95,9 +95,9 @@ NOTICE: ROLLBACK: no transaction in progress
Notes Notes
</title> </title>
<para> <para>
Use <xref linkend="SQL-COMMIT-TITLE" endterm="SQL-COMMIT-TITLE"> Use <xref linkend="SQL-COMMIT" endterm="SQL-COMMIT-TITLE">
to successfully terminate a transaction. to successfully terminate a transaction.
<xref linkend="SQL-ABORT-TITLE" endterm="SQL-ABORT-TITLE"> is a <xref linkend="SQL-ABORT" endterm="SQL-ABORT-TITLE"> is a
synonym for <command>ROLLBACK</command>. synonym for <command>ROLLBACK</command>.
</para> </para>
</refsect2> </refsect2>
......
doc/src/sgml/ref/select_into.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/select_into.sgml,v 1.7 2000/12/12 05:07:59 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/select_into.sgml,v 1.8 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -55,7 +55,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be: ...@@ -55,7 +55,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be:
</title> </title>
<para> <para>
All input fields are described in detail for All input fields are described in detail for
<xref linkend="sql-select-title" endterm="sql-select-title">. <xref linkend="sql-select" endterm="sql-select-title">.
</para> </para>
</refsect2> </refsect2>
...@@ -68,7 +68,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be: ...@@ -68,7 +68,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be:
</title> </title>
<para> <para>
All output fields are described in detail for All output fields are described in detail for
<xref linkend="sql-select-title" endterm="sql-select-title">. <xref linkend="sql-select" endterm="sql-select-title">.
</para> </para>
</refsect2> </refsect2>
</refsynopsisdiv> </refsynopsisdiv>
...@@ -87,7 +87,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be: ...@@ -87,7 +87,7 @@ where <replaceable class="PARAMETER">from_item</replaceable> can be:
<note> <note>
<para> <para>
<xref linkend="sql-createtableas-title" endterm="sql-createtableas-title"> <xref linkend="sql-createtableas" endterm="sql-createtableas-title">
is functionally equivalent to the <command>SELECT INTO</command> command. is functionally equivalent to the <command>SELECT INTO</command> command.
</para> </para>
</note> </note>
......
doc/src/sgml/ref/show.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/show.sgml,v 1.10 2000/06/18 21:24:54 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/show.sgml,v 1.11 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -27,7 +27,7 @@ SHOW <replaceable class="PARAMETER">name</replaceable> ...@@ -27,7 +27,7 @@ SHOW <replaceable class="PARAMETER">name</replaceable>
<listitem> <listitem>
<para> <para>
The name of a run-time parameter. See The name of a run-time parameter. See
<xref linkend="sql-set-title" endterm="sql-set-title"> <xref linkend="sql-set" endterm="sql-set-title">
for a list. for a list.
</para> </para>
</listitem> </listitem>
......
doc/src/sgml/ref/unlisten.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/unlisten.sgml,v 1.12 2000/10/05 19:48:19 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/unlisten.sgml,v 1.13 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -100,7 +100,7 @@ UNLISTEN { <replaceable class="PARAMETER">notifyname</replaceable> | * } ...@@ -100,7 +100,7 @@ UNLISTEN { <replaceable class="PARAMETER">notifyname</replaceable> | * }
</para> </para>
<para> <para>
<xref endterm="sql-notify-title" linkend="sql-notify-title"> <xref endterm="sql-notify-title" linkend="sql-notify">
contains a more extensive contains a more extensive
discussion of the use of <command>LISTEN</command> and discussion of the use of <command>LISTEN</command> and
<command>NOTIFY</command>. <command>NOTIFY</command>.
......
doc/src/sgml/ref/update.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/update.sgml,v 1.12 2000/10/05 19:57:23 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/update.sgml,v 1.13 2000/12/25 23:15:26 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -129,7 +129,7 @@ UPDATE <replaceable class="parameter">#</replaceable> ...@@ -129,7 +129,7 @@ UPDATE <replaceable class="parameter">#</replaceable>
<para> <para>
Array references use the same syntax found in Array references use the same syntax found in
<xref linkend="sql-select-title" endterm="sql-select-title">. <xref linkend="sql-select" endterm="sql-select-title">.
That is, either single array elements, a range of array That is, either single array elements, a range of array
elements or the entire array may be replaced with a single elements or the entire array may be replaced with a single
query. query.
......
doc/src/sgml/ref/vacuumdb.sgml
View file @ dccfd749
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuumdb.sgml,v 1.14 2000/11/22 01:41:13 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuumdb.sgml,v 1.15 2000/12/25 23:15:27 petere Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -202,7 +202,7 @@ Postgres documentation ...@@ -202,7 +202,7 @@ Postgres documentation
<para> <para>
Something went wrong. <application>vacuumdb</application> is only a wrapper Something went wrong. <application>vacuumdb</application> is only a wrapper
script. See <xref linkend="SQL-VACUUM" endterm="SQL-VACUUM-title"> script. See <xref linkend="SQL-VACUUM" endterm="SQL-VACUUM-title">
and <xref linkend="APP-PSQL" endterm="APP-PSQL-title"> for a detailed and <xref linkend="APP-PSQL"> for a detailed
discussion of error messages and potential problems. discussion of error messages and potential problems.
</para> </para>
</listitem> </listitem>
...@@ -234,7 +234,7 @@ Postgres documentation ...@@ -234,7 +234,7 @@ Postgres documentation
backend command backend command
<xref linkend="SQL-VACUUM" endterm="SQL-VACUUM-title"> via <xref linkend="SQL-VACUUM" endterm="SQL-VACUUM-title"> via
the <productname>Postgres</productname> interactive terminal the <productname>Postgres</productname> interactive terminal
<xref linkend="APP-PSQL" endterm="APP-PSQL-title">. There is no effective <xref linkend="APP-PSQL">. There is no effective
difference between vacuuming databases via this or other methods. difference between vacuuming databases via this or other methods.
<application>psql</application> must be found by the script and <application>psql</application> must be found by the script and
a database server must be running at the targeted host. Also, any default a database server must be running at the targeted host. Also, any default
......
doc/src/sgml/reference.sgml
View file @ dccfd749
<!-- reference.sgml <!-- reference.sgml
$Header: /cvsroot/pgsql/doc/src/sgml/reference.sgml,v 1.10 2000/11/25 13:20:05 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/reference.sgml,v 1.11 2000/12/25 23:15:26 petere Exp $
PostgreSQL Reference Manual PostgreSQL Reference Manual
--> -->
...@@ -119,7 +119,7 @@ Disable this chapter until we have more functions documented. ...@@ -119,7 +119,7 @@ Disable this chapter until we have more functions documented.
--> -->
<reference id="reference-client"> <reference id="reference-client">
<title>Client Applications</title> <title>PostgreSQL Client Applications</title>
<partintro> <partintro>
<para> <para>
...@@ -148,7 +148,7 @@ Disable this chapter until we have more functions documented. ...@@ -148,7 +148,7 @@ Disable this chapter until we have more functions documented.
</reference> </reference>
<reference id="reference-server"> <reference id="reference-server">
<title>Server Applications and Utilities</title> <title>PostgreSQL Server Applications</title>
<partintro> <partintro>
<para> <para>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment