The attached patch makes some minor improvements and cleanup to the
docs. Patch applied to HEAD.
-Neil
Index: doc/src/sgml/ref/create_operator.sgml
===================================================================
RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/create_operator.sgml,v
retrieving revision 1.42
diff -c -r1.42 create_operator.sgml
*** doc/src/sgml/ref/create_operator.sgml 25 Jun 2004 21:55:50 -0000 1.42
--- doc/src/sgml/ref/create_operator.sgml 18 Sep 2004 02:07:29 -0000
***************
*** 262,270 ****
</para>
<para>
! Use <command>DROP OPERATOR</command> to delete user-defined
! operators from a database. Use <command>ALTER OPERATOR</command>
! to modify operators in a database.
</para>
</refsect1>
--- 262,272 ----
</para>
<para>
! Use <xref linkend="sql-dropoperator"
! endterm="sql-dropoperator-title"> to delete user-defined operators
! from a database. Use <xref linkend="sql-alteroperator"
! endterm="sql-alteroperator-title"> to modify operators in a
! database.
</para>
</refsect1>
Index: doc/src/sgml/ref/deallocate.sgml
===================================================================
RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/deallocate.sgml,v
retrieving revision 1.5
diff -c -r1.5 deallocate.sgml
*** doc/src/sgml/ref/deallocate.sgml 29 Nov 2003 19:51:38 -0000 1.5
--- doc/src/sgml/ref/deallocate.sgml 18 Sep 2004 02:05:34 -0000
***************
*** 71,76 ****
--- 71,85 ----
statement, but it is only for use in embedded SQL.
</para>
</refsect1>
+
+ <refsect1>
+ <title>See Also</title>
+
+ <simplelist type="inline">
+ <member><xref linkend="sql-execute" endterm="sql-execute-title"></member>
+ <member><xref linkend="sql-prepare" endterm="sql-prepare-title"></member>
+ </simplelist>
+ </refsect1>
</refentry>
<!-- Keep this comment at the end of the file
Index: doc/src/sgml/ref/drop_trigger.sgml
===================================================================
RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/drop_trigger.sgml,v
retrieving revision 1.18
diff -c -r1.18 drop_trigger.sgml
*** doc/src/sgml/ref/drop_trigger.sgml 29 Nov 2003 19:51:38 -0000 1.18
--- doc/src/sgml/ref/drop_trigger.sgml 18 Sep 2004 02:10:02 -0000
***************
*** 51,58 ****
<term><replaceable class="PARAMETER">table</replaceable></term>
<listitem>
<para>
! The name (optionally schema-qualified) of a table for which the
! trigger is defined.
</para>
</listitem>
</varlistentry>
--- 51,58 ----
<term><replaceable class="PARAMETER">table</replaceable></term>
<listitem>
<para>
! The name (optionally schema-qualified) of the table for which
! the trigger is defined.
</para>
</listitem>
</varlistentry>
Index: doc/src/sgml/ref/execute.sgml
===================================================================
RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/execute.sgml,v
retrieving revision 1.10
diff -c -r1.10 execute.sgml
*** doc/src/sgml/ref/execute.sgml 22 Apr 2004 11:46:22 -0000 1.10
--- doc/src/sgml/ref/execute.sgml 18 Sep 2004 02:06:16 -0000
***************
*** 105,110 ****
--- 105,119 ----
syntax.
</para>
</refsect1>
+
+ <refsect1>
+ <title>See Also</title>
+
+ <simplelist type="inline">
+ <member><xref linkend="sql-deallocate" endterm="sql-deallocate-title"></member>
+ <member><xref linkend="sql-prepare" endterm="sql-prepare-title"></member>
+ </simplelist>
+ </refsect1>
</refentry>
<!-- Keep this comment at the end of the file
Index: doc/src/sgml/ref/postmaster.sgml
===================================================================
RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/postmaster.sgml,v
retrieving revision 1.51
diff -c -r1.51 postmaster.sgml
*** doc/src/sgml/ref/postmaster.sgml 11 Jul 2004 00:18:41 -0000 1.51
--- doc/src/sgml/ref/postmaster.sgml 19 Sep 2004 03:31:17 -0000
***************
*** 84,90 ****
point to a directory containing only configuration files:
<filename>postgresql.conf</>, <filename>pg_hba.conf</>, and
<filename>pg_ident.conf</>. You can then set
! <filename>postgresql.conf</>'s <varname>pgdata</> to point to the
data directory. You can also point just to the server configuration file
like <filename>postgresql.conf</> and set its variables to point to the
other configuration files and the data directory.
--- 84,90 ----
point to a directory containing only configuration files:
<filename>postgresql.conf</>, <filename>pg_hba.conf</>, and
<filename>pg_ident.conf</>. You can then set
! <filename>postgresql.conf</>'s <varname>pgdata</> variable to point to the
data directory. You can also point just to the server configuration file
like <filename>postgresql.conf</> and set its variables to point to the
other configuration files and the data directory.
***************
*** 164,171 ****
<term><option>-F</option></term>
<listitem>
<para>
! Disables <function>fsync</function> calls for performance
! improvement, at the risk of data corruption in event of a
system crash. Specifying this option is equivalent to
disabling the <xref linkend="guc-fsync"> configuration
parameter. Read the detailed documentation before using this!
--- 164,171 ----
<term><option>-F</option></term>
<listitem>
<para>
! Disables <function>fsync</function> calls for improved
! performance, at the risk of data corruption in the event of a
system crash. Specifying this option is equivalent to
disabling the <xref linkend="guc-fsync"> configuration
parameter. Read the detailed documentation before using this!
Index: doc/src/sgml/ref/prepare.sgml
===================================================================
RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/prepare.sgml,v
retrieving revision 1.12
diff -c -r1.12 prepare.sgml
*** doc/src/sgml/ref/prepare.sgml 19 Apr 2004 23:36:48 -0000 1.12
--- doc/src/sgml/ref/prepare.sgml 18 Sep 2004 02:04:48 -0000
***************
*** 129,135 ****
when planning prepared statements with parameters, the chosen plan
may be suboptimal. To examine the query plan
<productname>PostgreSQL</productname> has chosen for a prepared
! statement, use <command>EXPLAIN EXECUTE</command>.
</para>
<para>
--- 129,136 ----
when planning prepared statements with parameters, the chosen plan
may be suboptimal. To examine the query plan
<productname>PostgreSQL</productname> has chosen for a prepared
! statement, use <xref linkend="sql-explain"
! endterm="sql-explain-title">.
</para>
<para>
***************
*** 173,178 ****
--- 174,188 ----
syntax.
</para>
</refsect1>
+
+ <refsect1>
+ <title>See Also</title>
+
+ <simplelist type="inline">
+ <member><xref linkend="sql-deallocate" endterm="sql-deallocate-title"></member>
+ <member><xref linkend="sql-execute" endterm="sql-execute-title"></member>
+ </simplelist>
+ </refsect1>
</refentry>
<!-- Keep this comment at the end of the file
Index: doc/src/sgml/ref/rollback_to.sgml
===================================================================
RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/rollback_to.sgml,v
retrieving revision 1.3
diff -c -r1.3 rollback_to.sgml
*** doc/src/sgml/ref/rollback_to.sgml 24 Aug 2004 00:06:51 -0000 1.3
--- doc/src/sgml/ref/rollback_to.sgml 18 Sep 2004 02:14:12 -0000
***************
*** 146,154 ****
<simplelist type="inline">
<member><xref linkend="sql-begin" endterm="sql-begin-title"></member>
<member><xref linkend="sql-commit" endterm="sql-commit-title"></member>
- <member><xref linkend="sql-savepoint" endterm="sql-savepoint-title"></member>
<member><xref linkend="sql-release-savepoint" endterm="sql-release-savepoint-title"></member>
<member><xref linkend="sql-rollback" endterm="sql-rollback-title"></member>
</simplelist>
</refsect1>
</refentry>
--- 146,154 ----
<simplelist type="inline">
<member><xref linkend="sql-begin" endterm="sql-begin-title"></member>
<member><xref linkend="sql-commit" endterm="sql-commit-title"></member>
<member><xref linkend="sql-release-savepoint" endterm="sql-release-savepoint-title"></member>
<member><xref linkend="sql-rollback" endterm="sql-rollback-title"></member>
+ <member><xref linkend="sql-savepoint" endterm="sql-savepoint-title"></member>
</simplelist>
</refsect1>
</refentry>
Index: doc/src/sgml/ref/savepoint.sgml
===================================================================
RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/savepoint.sgml,v
retrieving revision 1.2
diff -c -r1.2 savepoint.sgml
*** doc/src/sgml/ref/savepoint.sgml 12 Aug 2004 19:12:21 -0000 1.2
--- doc/src/sgml/ref/savepoint.sgml 18 Sep 2004 02:14:40 -0000
***************
*** 126,135 ****
<simplelist type="inline">
<member><xref linkend="sql-begin" endterm="sql-begin-title"></member>
<member><xref linkend="sql-rollback" endterm="sql-rollback-title"></member>
<member><xref linkend="sql-rollback-to" endterm="sql-rollback-to-title"></member>
- <member><xref linkend="sql-release-savepoint" endterm="sql-release-savepoint-title"></member>
- <member><xref linkend="sql-commit" endterm="sql-commit-title"></member>
</simplelist>
</refsect1>
</refentry>
--- 126,135 ----
<simplelist type="inline">
<member><xref linkend="sql-begin" endterm="sql-begin-title"></member>
+ <member><xref linkend="sql-commit" endterm="sql-commit-title"></member>
+ <member><xref linkend="sql-release-savepoint" endterm="sql-release-savepoint-title"></member>
<member><xref linkend="sql-rollback" endterm="sql-rollback-title"></member>
<member><xref linkend="sql-rollback-to" endterm="sql-rollback-to-title"></member>
</simplelist>
</refsect1>
</refentry>
Index: doc/src/sgml/ref/set_transaction.sgml
===================================================================
RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/set_transaction.sgml,v
retrieving revision 1.21
diff -c -r1.21 set_transaction.sgml
*** doc/src/sgml/ref/set_transaction.sgml 14 Aug 2004 22:17:08 -0000 1.21
--- doc/src/sgml/ref/set_transaction.sgml 18 Sep 2004 02:18:10 -0000
***************
*** 30,42 ****
<title>Description</title>
<para>
! The <command>SET TRANSACTION</command> command sets the transaction
characteristics of the current transaction. It has no effect on any
subsequent transactions. <command>SET SESSION
CHARACTERISTICS</command> sets the default transaction
characteristics for subsequent transactions of a session. These
! defaults can be overridden by <command>SET TRANSACTION</command> for an
! individual transaction.
</para>
<para>
--- 30,42 ----
<title>Description</title>
<para>
! The <command>SET TRANSACTION</command> command sets the
characteristics of the current transaction. It has no effect on any
subsequent transactions. <command>SET SESSION
CHARACTERISTICS</command> sets the default transaction
characteristics for subsequent transactions of a session. These
! defaults can be overridden by <command>SET TRANSACTION</command>
! for an individual transaction.
</para>
<para>
Index: doc/src/sgml/ref/start_transaction.sgml
===================================================================
RCS file: /Users/neilc/local/cvs/pgsql-server/doc/src/sgml/ref/start_transaction.sgml,v
retrieving revision 1.13
diff -c -r1.13 start_transaction.sgml
*** doc/src/sgml/ref/start_transaction.sgml 12 Aug 2004 21:00:23 -0000 1.13
--- doc/src/sgml/ref/start_transaction.sgml 18 Sep 2004 02:16:39 -0000
***************
*** 85,92 ****
<member><xref linkend="sql-begin" endterm="sql-begin-title"></member>
<member><xref linkend="sql-commit" endterm="sql-commit-title"></member>
<member><xref linkend="sql-rollback" endterm="sql-rollback-title"></member>
- <member><xref linkend="sql-set-transaction" endterm="sql-set-transaction-title"></member>
<member><xref linkend="sql-savepoint" endterm="sql-savepoint-title"></member>
</simplelist>
</refsect1>
</refentry>
--- 85,92 ----
<member><xref linkend="sql-begin" endterm="sql-begin-title"></member>
<member><xref linkend="sql-commit" endterm="sql-commit-title"></member>
<member><xref linkend="sql-rollback" endterm="sql-rollback-title"></member>
<member><xref linkend="sql-savepoint" endterm="sql-savepoint-title"></member>
+ <member><xref linkend="sql-set-transaction" endterm="sql-set-transaction-title"></member>
</simplelist>
</refsect1>
</refentry>
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
