<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/analyze.sgml,v 1.15 2003/09/11 17:31:45 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/analyze.sgml,v 1.16 2003/09/12 23:04:45 tgl Exp $
PostgreSQL documentation
-->
</variablelist>
</refsect1>
+ <refsect1>
+ <title>Outputs</title>
+
+ <para>
+ When <literal>VERBOSE</> is specified, <command>ANALYZE</> emits
+ progress messages to indicate which table is currently being
+ processed. Various statistics about the tables are printed as well.
+ </para>
+ </refsect1>
+
<refsect1>
<title>Notes</title>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/clusterdb.sgml,v 1.14 2003/09/12 00:12:47 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/clusterdb.sgml,v 1.15 2003/09/12 23:04:45 tgl Exp $
PostgreSQL documentation
-->
this utility and via other methods for accessing the server.
</para>
- <para>
- In case of difficulty, see <xref linkend="SQL-CLUSTER"
- endterm="sql-cluster-title"> and <xref linkend="APP-PSQL"> for
- discussions of potential problems and error messages.
- The database server must be running at the
- targeted host. Also, any default connection settings and environment
- variables used by the <application>libpq</application> front-end
- library will apply.
- </para>
-
</refsect1>
</refsect1>
+ <refsect1>
+ <title>Diagnostics</title>
+
+ <para>
+ In case of difficulty, see <xref linkend="SQL-CLUSTER"
+ endterm="sql-cluster-title"> and <xref linkend="APP-PSQL"> for
+ discussions of potential problems and error messages.
+ The database server must be running at the
+ targeted host. Also, any default connection settings and environment
+ variables used by the <application>libpq</application> front-end
+ library will apply.
+ </para>
+
+ </refsect1>
+
+
<refsect1>
<title>Examples</title>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_language.sgml,v 1.35 2003/09/09 18:28:52 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_language.sgml,v 1.36 2003/09/12 23:04:45 tgl Exp $
PostgreSQL documentation
-->
for syntactical correctness, but it can also look at other
properties of the function, for example if the language cannot
handle certain argument types. To signal an error, the
- validator function should use the <function>elog()</function>
+ validator function should use the <function>ereport()</function>
function. The return value of the function is ignored.
</para>
</listitem>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/createdb.sgml,v 1.35 2003/09/12 00:12:47 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/createdb.sgml,v 1.36 2003/09/12 23:04:45 tgl Exp $
PostgreSQL documentation
-->
this utility and via other methods for accessing the server.
</para>
- <para>
- In case of difficulty, see <xref linkend="SQL-CREATEDATABASE"
- endterm="sql-createdatabase-title"> and <xref linkend="APP-PSQL"> for
- discussions of potential problems and error messages.
- The database server must be running at the
- targeted host. Also, any default connection settings and environment
- variables used by the <application>libpq</application> front-end
- library will apply.
- </para>
-
</refsect1>
</refsect1>
- <refsect1 id="R1-APP-CREATEDB-2">
+ <refsect1>
+ <title>Diagnostics</title>
+
+ <para>
+ In case of difficulty, see <xref linkend="SQL-CREATEDATABASE"
+ endterm="sql-createdatabase-title"> and <xref linkend="APP-PSQL"> for
+ discussions of potential problems and error messages.
+ The database server must be running at the
+ targeted host. Also, any default connection settings and environment
+ variables used by the <application>libpq</application> front-end
+ library will apply.
+ </para>
+
+ </refsect1>
+
+
+ <refsect1>
<title>Examples</title>
<para>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/createuser.sgml,v 1.37 2003/09/12 00:12:47 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/createuser.sgml,v 1.38 2003/09/12 23:04:46 tgl Exp $
PostgreSQL documentation
-->
this utility and via other methods for accessing the server.
</para>
- <para>
- In case of difficulty, see <xref linkend="SQL-CREATEUSER"
- endterm="sql-createuser-title"> and <xref linkend="APP-PSQL"> for
- discussions of potential problems and error messages.
- The database server must be running at the
- targeted host. Also, any default connection settings and environment
- variables used by the <application>libpq</application> front-end
- library will apply.
- </para>
-
</refsect1>
</refsect1>
+ <refsect1>
+ <title>Diagnostics</title>
+
+ <para>
+ In case of difficulty, see <xref linkend="SQL-CREATEUSER"
+ endterm="sql-createuser-title"> and <xref linkend="APP-PSQL"> for
+ discussions of potential problems and error messages.
+ The database server must be running at the
+ targeted host. Also, any default connection settings and environment
+ variables used by the <application>libpq</application> front-end
+ library will apply.
+ </para>
+
+ </refsect1>
+
+
<refsect1>
<title>Examples</title>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.24 2003/09/12 00:12:47 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.25 2003/09/12 23:04:46 tgl Exp $
PostgreSQL documentation
-->
this utility and via other methods for accessing the server.
</para>
- <para>
- In case of difficulty, see <xref linkend="SQL-DROPDATABASE"
- endterm="sql-dropdatabase-title"> and <xref linkend="APP-PSQL"> for
- discussions of potential problems and error messages.
- The database server must be running at the
- targeted host. Also, any default connection settings and environment
- variables used by the <application>libpq</application> front-end
- library will apply.
- </para>
-
</refsect1>
</refsect1>
- <refsect1 id="R1-APP-DROPDB-2">
+ <refsect1>
+ <title>Diagnostics</title>
+
+ <para>
+ In case of difficulty, see <xref linkend="SQL-DROPDATABASE"
+ endterm="sql-dropdatabase-title"> and <xref linkend="APP-PSQL"> for
+ discussions of potential problems and error messages.
+ The database server must be running at the
+ targeted host. Also, any default connection settings and environment
+ variables used by the <application>libpq</application> front-end
+ library will apply.
+ </para>
+
+ </refsect1>
+
+
+ <refsect1>
<title>Examples</title>
<para>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.29 2003/09/12 00:12:47 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.30 2003/09/12 23:04:46 tgl Exp $
PostgreSQL documentation
-->
this utility and via other methods for accessing the server.
</para>
- <para>
- In case of difficulty, see <xref linkend="SQL-DROPUSER"
- endterm="sql-dropuser-title"> and <xref linkend="APP-PSQL"> for
- discussions of potential problems and error messages.
- The database server must be running at the
- targeted host. Also, any default connection settings and environment
- variables used by the <application>libpq</application> front-end
- library will apply.
- </para>
-
</refsect1>
</refsect1>
+ <refsect1>
+ <title>Diagnostics</title>
+
+ <para>
+ In case of difficulty, see <xref linkend="SQL-DROPUSER"
+ endterm="sql-dropuser-title"> and <xref linkend="APP-PSQL"> for
+ discussions of potential problems and error messages.
+ The database server must be running at the
+ targeted host. Also, any default connection settings and environment
+ variables used by the <application>libpq</application> front-end
+ library will apply.
+ </para>
+
+ </refsect1>
+
+
<refsect1>
<title>Examples</title>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/listen.sgml,v 1.18 2003/09/12 00:12:47 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/listen.sgml,v 1.19 2003/09/12 23:04:46 tgl Exp $
PostgreSQL documentation
-->
<title>Examples</title>
<para>
- Configure and execute a listen/notify sequence from <application>psql</application>:
+ Configure and execute a listen/notify sequence from
+ <application>psql</application>:
+
<programlisting>
LISTEN virtual;
NOTIFY virtual;
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/notify.sgml,v 1.22 2003/09/09 18:28:53 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/notify.sgml,v 1.23 2003/09/12 23:04:46 tgl Exp $
PostgreSQL documentation
-->
<programlisting>
LISTEN virtual;
NOTIFY virtual;
-Asynchronous NOTIFY 'virtual' from backend with pid '8448' received.
+Asynchronous notification "virtual" received from server process with PID 8448.
</programlisting>
</para>
</refsect1>
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/unlisten.sgml,v 1.23 2003/09/09 18:28:53 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/unlisten.sgml,v 1.24 2003/09/12 23:04:46 tgl Exp $
PostgreSQL documentation
-->
<programlisting>
LISTEN virtual;
NOTIFY virtual;
-Asynchronous NOTIFY 'virtual' from backend with pid '8448' received
+Asynchronous notification "virtual" received from server process with PID 8448.
</programlisting>
</para>
<para>
- Once <command>UNLISTEN</> has been executed, further <command>NOTIFY</> commands will be
- ignored:
+ Once <command>UNLISTEN</> has been executed, further <command>NOTIFY</>
+ commands will be ignored:
<programlisting>
UNLISTEN virtual;
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuumdb.sgml,v 1.32 2003/09/12 00:12:47 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuumdb.sgml,v 1.33 2003/09/12 23:04:46 tgl Exp $
PostgreSQL documentation
-->
this utility and via other methods for accessing the server.
</para>
- <para>
- In case of difficulty, see <xref linkend="SQL-VACUUM"
- endterm="sql-vacuum-title"> and <xref linkend="APP-PSQL"> for
- discussions of potential problems and error messages.
- The database server must be running at the
- targeted host. Also, any default connection settings and environment
- variables used by the <application>libpq</application> front-end
- library will apply.
- </para>
-
- <para>
- <application>vacuumdb</application> might need to connect several
- times to the <productname>PostgreSQL</productname> server, asking
- for a password each time. It is convenient to have a
- <filename>$HOME/.pgpass</> file in such cases. See <xref
- linkend="libpq-pgpass"> for more information.
- </para>
-
</refsect1>
</refsect1>
+ <refsect1>
+ <title>Diagnostics</title>
+
+ <para>
+ In case of difficulty, see <xref linkend="SQL-VACUUM"
+ endterm="sql-vacuum-title"> and <xref linkend="APP-PSQL"> for
+ discussions of potential problems and error messages.
+ The database server must be running at the
+ targeted host. Also, any default connection settings and environment
+ variables used by the <application>libpq</application> front-end
+ library will apply.
+ </para>
+
+ </refsect1>
+
+
+ <refsect1>
+ <title>Notes</title>
+
+ <para>
+ <application>vacuumdb</application> might need to connect several
+ times to the <productname>PostgreSQL</productname> server, asking
+ for a password each time. It is convenient to have a
+ <filename>$HOME/.pgpass</> file in such cases. See <xref
+ linkend="libpq-pgpass"> for more information.
+ </para>
+ </refsect1>
+
<refsect1>
<title>Examples</title>