aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat
-rw-r--r--doc/src/sgml/client-auth.sgml31
-rw-r--r--doc/src/sgml/func.sgml4
-rw-r--r--doc/src/sgml/information_schema.sgml238
-rw-r--r--doc/src/sgml/installation.sgml17
-rw-r--r--doc/src/sgml/jdbc.sgml32
-rw-r--r--doc/src/sgml/libpq.sgml14
-rw-r--r--doc/src/sgml/mvcc.sgml12
-rw-r--r--doc/src/sgml/ref/copy.sgml6
-rw-r--r--doc/src/sgml/ref/create_table_as.sgml26
-rw-r--r--doc/src/sgml/ref/postmaster.sgml24
-rw-r--r--doc/src/sgml/ref/select_into.sgml25
-rw-r--r--doc/src/sgml/rules.sgml8
-rw-r--r--doc/src/sgml/runtime.sgml4
13 files changed, 225 insertions, 216 deletions
diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index bbe84c13ede..34322aeba78 100644
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.61 2003/11/29 19:51:36 pgsql Exp $
+$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.62 2003/12/13 23:59:06 neilc Exp $
-->
<chapter id="client-authentication">
@@ -111,10 +111,13 @@ hostnossl <replaceable>database</replaceable> <replaceable>user</replaceable>
<term><literal>host</literal></term>
<listitem>
<para>
- This record matches connection attempts using TCP/IP networks.
+ This record matches connection attempts made using TCP/IP.
Note that TCP/IP connections are disabled unless the server is
started with the <option>-i</option> option or the
- <varname>tcpip_socket</> configuration parameter is enabled.
+ <varname>tcpip_socket</> configuration parameter is
+ enabled. <literal>host</literal> records match either
+ <acronym>SSL</acronym> or non-<acronym>SSL</acronym> connection
+ attempts.
</para>
</listitem>
</varlistentry>
@@ -123,17 +126,17 @@ hostnossl <replaceable>database</replaceable> <replaceable>user</replaceable>
<term><literal>hostssl</literal></term>
<listitem>
<para>
- This record matches connection attempts using SSL over TCP/IP.
- <literal>host</literal> records will match either SSL or
- non-SSL connection attempts, but <literal>hostssl</literal>
- records require SSL connections.
+ This record matches connection attempts made using TCP/IP. In
+ addition, this record requires that the connection is made with
+ <acronym>SSL</acronym>.
</para>
<para>
- To make use of this option the server must be built
- with SSL support enabled. Furthermore, SSL must be enabled by
- enabling the <varname>ssl</varname> configuration parameter
- (see <xref linkend="runtime-config"> for more information).
+ To make use of this option the server must be built with
+ <acronym>SSL</acronym> support enabled. Furthermore,
+ <acronym>SSL</acronym> must be enabled by setting the
+ <varname>ssl</varname> configuration parameter (see <xref
+ linkend="ssl-tcp"> for more information).
</para>
</listitem>
</varlistentry>
@@ -143,8 +146,8 @@ hostnossl <replaceable>database</replaceable> <replaceable>user</replaceable>
<listitem>
<para>
This record is similar to <literal>hostssl</> but with the
- opposite logic: it matches only regular connection attempts not
- using SSL.
+ opposite logic: it only matches connection attempts made over
+ TCP/IP that do not use <acronym>SSL</acronym>.
</para>
</listitem>
</varlistentry>
@@ -593,7 +596,7 @@ local db1,db2,@demodbs all md5
<quote>sniffing</> attacks then <literal>md5</> is preferred, with
<literal>crypt</> a second choice if you must support pre-7.2
clients. Plain <literal>password</> should especially be avoided for
- connections over the open Internet (unless you use SSL, SSH, or
+ connections over the open Internet (unless you use <acronym>SSL</acronym>, SSH, or
other communications security wrappers around the connection).
</para>
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 923243aef84..d73199fb20e 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.180 2003/11/29 19:51:37 pgsql Exp $
+$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.181 2003/12/13 23:59:06 neilc Exp $
PostgreSQL documentation
-->
@@ -6117,7 +6117,7 @@ SELECT TIMESTAMP 'now';
<sect1 id="functions-sequence">
- <title>Sequence-Manipulation Functions</title>
+ <title>Sequence Manipulation Functions</title>
<indexterm>
<primary>sequence</primary>
diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml
index f6ff552f115..9193280ea6c 100644
--- a/doc/src/sgml/information_schema.sgml
+++ b/doc/src/sgml/information_schema.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/information_schema.sgml,v 1.12 2003/11/29 19:51:37 pgsql Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/information_schema.sgml,v 1.13 2003/12/13 23:59:06 neilc Exp $ -->
<chapter id="information-schema">
<title>The Information Schema</title>
@@ -183,7 +183,7 @@
<row>
<entry><literal>is_grantable</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
</tbody>
</tgroup>
@@ -669,37 +669,37 @@
<row>
<entry><literal>character_set_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_set_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_set_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
@@ -758,25 +758,25 @@
<row>
<entry><literal>scope_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>scope_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>scope_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>maximum_cardinality</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, because arrays always have unlimited maximum cardinality in PostgreSQL</entry>
+ <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>PostgreSQL</></entry>
</row>
<row>
@@ -795,7 +795,7 @@
<row>
<entry><literal>is_self_referencing</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
</tbody>
</tgroup>
@@ -1279,37 +1279,37 @@
<row>
<entry><literal>character_set_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_set_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_set_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
@@ -1401,25 +1401,25 @@
<row>
<entry><literal>scope_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>scope_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>scope_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>maximum_cardinality</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, because arrays always have unlimited maximum cardinality in PostgreSQL</entry>
+ <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>PostgreSQL</></entry>
</row>
<row>
@@ -1541,85 +1541,85 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>character_maximum_length</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to array element data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_octet_length</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to array element data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_set_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_set_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_set_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>numeric_precision</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to array element data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>numeric_precision_radix</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to array element data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>numeric_scale</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to array element data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>datetime_precision</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to array element data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>interval_type</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Always null, since this information is not applied to array element data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>interval_precision</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Always null, since this information is not applied to array element data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to array element data types in <productname>PostgreSQL</></entry>
</row>
<row>
@@ -1657,25 +1657,25 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>scope_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>scope_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>scope_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>maximum_cardinality</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, because arrays always have unlimited maximum cardinality in PostgreSQL</entry>
+ <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>PostgreSQL</></entry>
</row>
<row>
@@ -1883,19 +1883,19 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>is_result</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>as_locator</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>parameter_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Always null, since PostgreSQL does not support named parameters</entry>
+ <entry>Always null, since <productname>PostgreSQL</> does not support named parameters</entry>
</row>
<row>
@@ -1914,85 +1914,85 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>character_maximum_length</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to parameter data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_octet_length</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to parameter data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_set_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_set_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_set_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>numeric_precision</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to parameter data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>numeric_precision_radix</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to parameter data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>numeric_scale</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to parameter data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>datetime_precision</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to parameter data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>interval_type</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Always null, since this information is not applied to parameter data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>interval_precision</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Always null, since this information is not applied to parameter data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to parameter data types in <productname>PostgreSQL</></entry>
</row>
<row>
@@ -2024,25 +2024,25 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>scope_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>scope_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>scope_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>maximum_cardinality</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, because arrays always have unlimited maximum cardinality in PostgreSQL</entry>
+ <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>PostgreSQL</></entry>
</row>
<row>
@@ -2408,7 +2408,7 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>with_hierarchy</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
</tbody>
</tgroup>
@@ -2670,37 +2670,37 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>module_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>module_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>module_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>udt_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>udt_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>udt_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
@@ -2719,85 +2719,85 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>character_maximum_length</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to return data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_octet_length</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to return data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_set_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_set_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>character_set_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>collation_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>numeric_precision</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to return data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>numeric_precision_radix</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to return data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>numeric_scale</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to return data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>datetime_precision</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, since this information is not applied to return data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>interval_type</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Always null, since this information is not applied to return data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>interval_precision</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Always null, since this information is not applied to return data types in PostgreSQL</entry>
+ <entry>Always null, since this information is not applied to return data types in <productname>PostgreSQL</></entry>
</row>
<row>
@@ -2829,25 +2829,25 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>scope_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>scope_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>scope_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>maximum_cardinality</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Always null, because arrays always have unlimited maximum cardinality in PostgreSQL</entry>
+ <entry>Always null, because arrays always have unlimited maximum cardinality in <productname>PostgreSQL</></entry>
</row>
<row>
@@ -2908,7 +2908,7 @@ ORDER BY c.ordinal_position;
<entry><type>character_data</type></entry>
<entry>
Always <literal>GENERAL</literal> (The SQL standard defines
- other parameter styles, which are not available in PostgreSQL.)
+ other parameter styles, which are not available in <productname>PostgreSQL</>.)
</entry>
</row>
@@ -2919,7 +2919,7 @@ ORDER BY c.ordinal_position;
If the function is declared immutable (called deterministic in
the SQL standard), then <literal>YES</literal>, else
<literal>NO</literal>. (You cannot query the other volatility
- levels available in PostgreSQL through the information schema.)
+ levels available in <productname>PostgreSQL</> through the information schema.)
</entry>
</row>
@@ -2929,7 +2929,7 @@ ORDER BY c.ordinal_position;
<entry>
Always <literal>MODIFIES</literal>, meaning that the function
possibly modifies SQL data. This information is not useful for
- PostgreSQL.
+ <productname>PostgreSQL</>.
</entry>
</row>
@@ -2946,7 +2946,7 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>sql_path</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
@@ -2955,26 +2955,26 @@ ORDER BY c.ordinal_position;
<entry>
Always <literal>YES</literal> (The opposite would be a method
of a user-defined type, which is a feature not available in
- PostgreSQL.)
+ <productname>PostgreSQL</>.)
</entry>
</row>
<row>
<entry><literal>max_dynamic_result_sets</literal></entry>
<entry><type>cardinal_number</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>is_user_defined_cast</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>is_implicitly_invocable</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
@@ -2991,25 +2991,25 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>to_sql_specific_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>to_sql_specific_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>to_sql_specific_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>as_locator</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
</tbody>
</tgroup>
@@ -3058,25 +3058,25 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>default_character_set_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>default_character_set_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>default_character_set_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>sql_path</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
</tbody>
</tgroup>
@@ -3136,7 +3136,7 @@ ORDER BY c.ordinal_position;
<entry><type>character_data</type></entry>
<entry>
<literal>YES</literal> if the feature is fully supported by the
- current version of PostgreSQL, <literal>NO</literal> if not
+ current version of <productname>PostgreSQL</>, <literal>NO</literal> if not
</entry>
</row>
@@ -3144,7 +3144,7 @@ ORDER BY c.ordinal_position;
<entry><literal>is_verified_by</literal></entry>
<entry><type>character_data</type></entry>
<entry>
- Always null, since the PostgreSQL development group does not
+ Always null, since the <productname>PostgreSQL</> development group does not
perform formal testing of feature conformance
</entry>
</row>
@@ -3306,7 +3306,7 @@ ORDER BY c.ordinal_position;
<entry><type>character_data</type></entry>
<entry>
The programming language, if the binding style is
- <literal>EMBEDDED</literal>, else null. PostgreSQL only
+ <literal>EMBEDDED</literal>, else null. <productname>PostgreSQL</> only
supports the language C.
</entry>
</row>
@@ -3355,7 +3355,7 @@ ORDER BY c.ordinal_position;
<entry><type>character_data</type></entry>
<entry>
<literal>YES</literal> if the package is fully supported by the
- current version of PostgreSQL, <literal>NO</literal> if not
+ current version of <productname>PostgreSQL</>, <literal>NO</literal> if not
</entry>
</row>
@@ -3363,7 +3363,7 @@ ORDER BY c.ordinal_position;
<entry><literal>is_verified_by</literal></entry>
<entry><type>character_data</type></entry>
<entry>
- Always null, since the PostgreSQL development group does not
+ Always null, since the <productname>PostgreSQL</> development group does not
perform formal testing of feature conformance
</entry>
</row>
@@ -3443,7 +3443,7 @@ ORDER BY c.ordinal_position;
<para>
The table <literal>sql_sizing_profiles</literal> contains
information about the <literal>sql_sizing</literal> values that are
- required by various profiles of the SQL standard. PostgreSQL does
+ required by various profiles of the SQL standard. <productname>PostgreSQL</> does
not track any SQL profiles, so this table is empty.
</para>
@@ -3656,7 +3656,7 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>with_hierarchy</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
</tbody>
</tgroup>
@@ -3726,31 +3726,31 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>self_referencing_column_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>reference_generation</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>user_defined_type_catalog</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>user_defined_type_schema</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>user_defined_type_name</literal></entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
</tbody>
</tgroup>
@@ -3836,7 +3836,7 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>action_condition</literal</entry>
<entry><type>character_data</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
@@ -3871,13 +3871,13 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>condition_reference_old_table</literal</entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
<entry><literal>condition_reference_new_table</literal</entry>
<entry><type>sql_identifier</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
</tbody>
</tgroup>
@@ -4206,7 +4206,7 @@ ORDER BY c.ordinal_position;
<row>
<entry><literal>check_option</literal></entry>
<entry><type>character_data</type></entry>
- <entry>Applies to a feature not available in PostgreSQL</entry>
+ <entry>Applies to a feature not available in <productname>PostgreSQL</></entry>
</row>
<row>
diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml
index 26cc7add5d6..eb72a170fa4 100644
--- a/doc/src/sgml/installation.sgml
+++ b/doc/src/sgml/installation.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.188 2003/12/11 19:56:54 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.189 2003/12/13 23:59:06 neilc Exp $ -->
<chapter id="installation">
<title><![%standalone-include[<productname>PostgreSQL</>]]>
@@ -268,7 +268,7 @@ JAVACMD=$JAVA_HOME/bin/java
<listitem>
<para>
- <application>Kerberos</>, <application>OpenSSL</>, or <application>PAM</>,
+ <application>Kerberos</>, <productname>OpenSSL</>, or <application>PAM</>,
if you want to support authentication using these services.
</para>
</listitem>
@@ -893,11 +893,14 @@ JAVACMD=$JAVA_HOME/bin/java
<term><option>--disable-spinlocks</option></term>
<listitem>
<para>
- Allow the builds to succeed even if PostgreSQL has no CPU
- spinlock support for the platform. The lack of spinlock
- support will result in poor performance; therefore, this
- option should only be used if the build aborts and informs
- you that the platform lacks spinlock support.
+ Allow the build to succeed even if <productname>PostgreSQL</>
+ has no CPU spinlock support for the platform. The lack of
+ spinlock support will result in poor performance; therefore,
+ this option should only be used if the build aborts and
+ informs you that the platform lacks spinlock support. If this
+ option is required to build <productname>PostgreSQL</> on
+ your platform, please report the problem to the
+ <productname>PostgreSQL</> developers.
</para>
</listitem>
</varlistentry>
diff --git a/doc/src/sgml/jdbc.sgml b/doc/src/sgml/jdbc.sgml
index 44096b7eae5..e2f0f393474 100644
--- a/doc/src/sgml/jdbc.sgml
+++ b/doc/src/sgml/jdbc.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/jdbc.sgml,v 1.51 2003/11/29 19:51:37 pgsql Exp $
+$PostgreSQL: pgsql/doc/src/sgml/jdbc.sgml,v 1.52 2003/12/13 23:59:06 neilc Exp $
-->
<chapter id="jdbc">
@@ -98,8 +98,8 @@ $PostgreSQL: pgsql/doc/src/sgml/jdbc.sgml,v 1.51 2003/11/29 19:51:37 pgsql Exp $
For instance, assume we have an application that uses the
<acronym>JDBC</acronym> driver to access a database, and that
application is installed as
- <filename>/usr/local/lib/myapp.jar</filename>. The PostgreSQL
- <acronym>JDBC</> driver installed as
+ <filename>/usr/local/lib/myapp.jar</filename>. The
+ <productname>PostgreSQL</> <acronym>JDBC</> driver installed as
<filename>/usr/local/pgsql/share/java/postgresql.jar</>. To run
the application, we would use:
<programlisting>
@@ -119,9 +119,9 @@ java MyApp
<para>
Because Java only uses TCP/IP connections, the
- <application>PostgreSQL</application> server must be configured to
- accept TCP/IP connections. This can be done by setting
- <literal>tcpip_socket = true</literal> in the
+ <productname>PostgreSQL</productname> server must be configured to
+ accept TCP/IP connections. This can be done by setting
+ <literal>tcpip_socket = true</literal> in the
<filename>postgresql.conf</filename> file or by supplying the
<option>-i</option> option flag when starting
<command>postmaster</command>.
@@ -239,7 +239,7 @@ java -Djdbc.drivers=org.postgresql.Driver example.ImageViewer
<para>
With <acronym>JDBC</acronym>, a database is represented by a
<acronym>URL</acronym> (Uniform Resource Locator). With
- <application>PostgreSQL</application>, this takes one of the
+ <productname>PostgreSQL</productname>, this takes one of the
following forms:
<itemizedlist>
@@ -720,7 +720,7 @@ st.close();
</indexterm>
<para>
- <application>PostgreSQL</application> provides two distinct ways to
+ <productname>PostgreSQL</productname> provides two distinct ways to
store binary data. Binary data can be stored in a table using
the data type <type>bytea</type> or by using the Large Object
feature which stores the binary data in a separate table in a special
@@ -770,12 +770,11 @@ st.close();
</para>
<para>
- To use the Large Object functionality you can use either the
- <classname>LargeObject</classname> class
- provided by the <application>PostgreSQL</application>
- <acronym>JDBC</acronym> driver, or by using the
- <function>getBLOB()</function> and <function>setBLOB()</function>
- methods.
+ To use the Large Object functionality you can use either the
+ <classname>LargeObject</classname> class provided by the
+ <productname>PostgreSQL</> <acronym>JDBC</acronym> driver, or by
+ using the <function>getBLOB()</function> and
+ <function>setBLOB()</function> methods.
</para>
<important>
@@ -800,7 +799,8 @@ st.close();
<para>
<xref linkend="jdbc-binary-data-example"> contains some examples on
- how to process binary data using the PostgreSQL <acronym>JDBC</> driver.
+ how to process binary data using the <productname>PostgreSQL</>
+ <acronym>JDBC</> driver.
</para>
<example id="jdbc-binary-data-example">
@@ -948,7 +948,7 @@ ps.close();
<sect1 id="jdbc-ext">
- <title><application>PostgreSQL</application> Extensions to the
+ <title><productname>PostgreSQL</productname> Extensions to the
<acronym>JDBC</acronym> <acronym>API</acronym></title>
<para>
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 81b1672e4dd..248d8646af2 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.143 2003/11/29 19:51:37 pgsql Exp $
+$PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.144 2003/12/13 23:59:06 neilc Exp $
-->
<chapter id="libpq">
@@ -3575,12 +3575,12 @@ If the permissions are less strict than this, the file will be ignored.
<para>
<application>libpq</application> is reentrant and thread-safe if the
<filename>configure</filename> command-line option
-<literal>--enable-thread-safety</> has been used when the PostgreSQL
-distribution was built.
-In addition, you might need to use additional compiler command-line
-options when you compile your application code. Refer to your system's
-documentation for information about how to build thread-enabled
-applications.
+<literal>--enable-thread-safety</> has been used when the
+<productname>PostgreSQL</productname> distribution was built. In
+addition, you might need to use additional compiler command-line
+options when you compile your application code. Refer to your
+system's documentation for information about how to build
+thread-enabled applications.
</para>
<para>
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index f86dcbe21b4..ebbdf6291f7 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.42 2003/11/29 19:51:37 pgsql Exp $
+$PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.43 2003/12/13 23:59:06 neilc Exp $
-->
<chapter id="mvcc">
@@ -215,11 +215,11 @@ $PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.42 2003/11/29 19:51:37 pgsql Exp $
isolation level may be stricter than what you select. This is
permitted by the SQL standard: the four isolation levels only
define which phenomena must not happen, they do not define which
- phenomena must happen. The reason that PostgreSQL only provides
- two isolation levels is that this is the only sensible way to map
- the isolation levels to the multiversion concurrency control
- architecture. The behavior of the available isolation levels is
- detailed in the following subsections.
+ phenomena must happen. The reason that <productname>PostgreSQL</>
+ only provides two isolation levels is that this is the only
+ sensible way to map the isolation levels to the multiversion
+ concurrency control architecture. The behavior of the available
+ isolation levels is detailed in the following subsections.
</para>
<para>
diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index c510803af62..1e12cbf3516 100644
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.54 2003/11/29 19:51:38 pgsql Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.55 2003/12/13 23:59:07 neilc Exp $
PostgreSQL documentation
-->
@@ -584,8 +584,8 @@ ZW ZIMBABWE
</para>
<para>
- The following syntax was used before PostgreSQL version 7.3 and is
- still supported:
+ The following syntax was used before <productname>PostgreSQL</>
+ version 7.3 and is still supported:
<synopsis>
COPY [ BINARY ] <replaceable class="parameter">tablename</replaceable> [ WITH OIDS ]
diff --git a/doc/src/sgml/ref/create_table_as.sgml b/doc/src/sgml/ref/create_table_as.sgml
index a7382abfdc9..3bc5668b9fe 100644
--- a/doc/src/sgml/ref/create_table_as.sgml
+++ b/doc/src/sgml/ref/create_table_as.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.18 2003/12/01 22:07:58 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.19 2003/12/13 23:59:07 neilc Exp $
PostgreSQL documentation
-->
@@ -125,17 +125,19 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } ] TABLE <replaceable>table_name
</para>
<para>
- Prior to PostgreSQL 7.5, <command>CREATE TABLE AS</command> always
- included OIDs in the table it produced. Furthermore, these OIDs
- were newly generated: they were distinct from the OIDs of any of
- the rows in the source tables of the <command>SELECT</command> or
- <command>EXECUTE</command> statement. Therefore, if <command>CREATE
- TABLE AS</command> was frequently executed, the OID counter would
- be rapidly incremented. As of PostgreSQL 7.5, the inclusion of OIDs
- in the table generated by <command>CREATE TABLE AS</command> is
- controlled by the <varname>default_with_oids</varname> configuration
- variable. This variable currently defaults to true, but will likely
- default to false in a future release of <productname>PostgreSQL</>.
+ Prior to <productname>PostgreSQL</> 7.5, <command>CREATE TABLE
+ AS</command> always included OIDs in the table it
+ produced. Furthermore, these OIDs were newly generated: they were
+ distinct from the OIDs of any of the rows in the source tables of
+ the <command>SELECT</command> or <command>EXECUTE</command>
+ statement. Therefore, if <command>CREATE TABLE AS</command> was
+ frequently executed, the OID counter would be rapidly
+ incremented. As of <productname>PostgreSQL</> 7.5, the inclusion of
+ OIDs in the table generated by <command>CREATE TABLE AS</command>
+ is controlled by the <varname>default_with_oids</varname>
+ configuration variable. This variable currently defaults to true,
+ but will likely default to false in a future release of
+ <productname>PostgreSQL</>.
</para>
</refsect1>
diff --git a/doc/src/sgml/ref/postmaster.sgml b/doc/src/sgml/ref/postmaster.sgml
index 258af3f08ee..f3e55507cf0 100644
--- a/doc/src/sgml/ref/postmaster.sgml
+++ b/doc/src/sgml/ref/postmaster.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.42 2003/11/29 19:51:39 pgsql Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.43 2003/12/13 23:59:07 neilc Exp $
PostgreSQL documentation
-->
@@ -452,17 +452,17 @@ PostgreSQL documentation
</para>
<para>
- A failure message indicating inability to bind to a port may indicate
- that that port is already in use by some non-PostgreSQL process.
- You may also get this error if you terminate the
- <command>postmaster</command>
- and immediately restart it using the same port; in this case, you must
- simply wait a few seconds until the operating system closes the port
- before trying again. Finally, you may get this error if you specify
- a port number that your operating system considers to be reserved.
- For example, many versions of Unix consider port numbers under 1024 to
- be <quote>trusted</quote>
- and only permit the Unix superuser to access them.
+ A failure message indicating inability to bind to a port may
+ indicate that that port is already in use by some
+ non-<productname>PostgreSQL</productname> process. You may also
+ get this error if you terminate the <command>postmaster</command>
+ and immediately restart it using the same port; in this case, you
+ must simply wait a few seconds until the operating system closes
+ the port before trying again. Finally, you may get this error if
+ you specify a port number that your operating system considers to
+ be reserved. For example, many versions of Unix consider port
+ numbers under 1024 to be <quote>trusted</quote> and only permit
+ the Unix superuser to access them.
</para>
</refsect1>
diff --git a/doc/src/sgml/ref/select_into.sgml b/doc/src/sgml/ref/select_into.sgml
index 1261f3cd4b5..0585726aac9 100644
--- a/doc/src/sgml/ref/select_into.sgml
+++ b/doc/src/sgml/ref/select_into.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/select_into.sgml,v 1.26 2003/12/01 22:07:58 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/select_into.sgml,v 1.27 2003/12/13 23:59:07 neilc Exp $
PostgreSQL documentation
-->
@@ -94,17 +94,18 @@ SELECT [ ALL | DISTINCT [ ON ( <replaceable class="PARAMETER">expression</replac
</para>
<para>
- Prior to PostgreSQL 7.5, the table created by <command>SELECT
- INTO</command> always included OIDs. Furthermore, these OIDs were
- newly generated: they were distinct from the OIDs of any of the
- rows in the source tables of the <command>SELECT INTO</command>
- statement. Therefore, if <command>SELECT INTO</command> was
- frequently executed, the OID counter would be rapidly
- incremented. As of PostgreSQL 7.5, the inclusion of OIDs in the
- table created by <command>SELECT INTO</command> is controlled by
- the <varname>default_with_oids</varname> configuration
- variable. This variable currently defaults to true, but will likely
- default to false in a future release of <productname>PostgreSQL</>.
+ Prior to <productname>PostgreSQL</> 7.5, the table created by
+ <command>SELECT INTO</command> always included OIDs. Furthermore,
+ these OIDs were newly generated: they were distinct from the OIDs
+ of any of the rows in the source tables of the <command>SELECT
+ INTO</command> statement. Therefore, if <command>SELECT
+ INTO</command> was frequently executed, the OID counter would be
+ rapidly incremented. As of <productname>PostgreSQL</> 7.5, the
+ inclusion of OIDs in the table created by <command>SELECT
+ INTO</command> is controlled by the
+ <varname>default_with_oids</varname> configuration variable. This
+ variable currently defaults to true, but will likely default to
+ false in a future release of <productname>PostgreSQL</>.
</para>
</refsect1>
diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml
index d3096c8447e..c719a651de1 100644
--- a/doc/src/sgml/rules.sgml
+++ b/doc/src/sgml/rules.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.32 2003/11/29 19:51:37 pgsql Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.33 2003/12/13 23:59:06 neilc Exp $ -->
<Chapter Id="rules">
<Title>The Rule System</Title>
@@ -1825,9 +1825,9 @@ GRANT SELECT ON phone_number TO secretary;
</listitem>
</itemizedlist>
- (This system was established in PostgreSQL 7.3. In versions
- before that, the command status might show different results when
- rules exist.)
+ (This system was established in <productname>PostgreSQL</> 7.3.
+ In versions before that, the command status might show different
+ results when rules exist.)
</Para>
<Para>
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 49f48ca3be3..34fc350a6c5 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.226 2003/12/06 23:10:23 joe Exp $
+$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.227 2003/12/13 23:59:06 neilc Exp $
-->
<Chapter Id="runtime">
@@ -3551,7 +3551,7 @@ $ <userinput>kill -INT `head -1 /usr/local/pgsql/data/postmaster.pid`</userinput
The server will listen for both standard and <acronym>SSL</>
connections on the same TCP port, and will negotiate with any
connecting client on whether to use <acronym>SSL</>. See <xref
- linkend="client-authentication"> about how to force the server to
+ linkend="auth-pg-hba-conf"> about how to force the server to
require use of <acronym>SSL</> for certain connections.
</para>
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-29 21:13:27 +0000