Index: doc/src/sgml/admin.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/admin.sgml,v
retrieving revision 1.40
diff -c -r1.40 admin.sgml
*** doc/src/sgml/admin.sgml	24 Oct 2002 17:48:54 -0000	1.40
--- doc/src/sgml/admin.sgml	10 Nov 2002 22:24:33 -0000
***************
*** 25,37 ****
     <title>What's In This Book</title>
  
     <para>
!     This book covers topics that are of interest to a PostgreSQL
!     database administrator.  This includes installation of the
!     software, set up and configuration of the server, management of
!     users and databases, and maintenance tasks.  Anyone who runs a
!     PostgreSQL server, either for personal use, but especially in
!     production, should be familiar with the topics covered in this
!     book.
     </para>
  
     <para>
--- 25,37 ----
     <title>What's In This Book</title>
  
     <para>
!     This book covers topics that are of interest to a
!     <productname>PostgreSQL</> database administrator.  This includes
!     installation of the software, set up and configuration of the
!     server, management of users and databases, and maintenance tasks.
!     Anyone who runs a <productname>PostgreSQL</> server, either for
!     personal use, but especially in production, should be familiar
!     with the topics covered in this book.
     </para>
  
     <para>
***************
*** 49,57 ****
      up their own server can begin their exploration with this book.
      The rest of this book which is about tuning and management
      presupposes that the reader is familiar with the general use of
!     the PostgreSQL database system.  Readers are encouraged to look at
!     the &cite-tutorial; and the &cite-user; for additional
!     information.
     </para>
  
     <para>
--- 49,57 ----
      up their own server can begin their exploration with this book.
      The rest of this book which is about tuning and management
      presupposes that the reader is familiar with the general use of
!     the <productname>PostgreSQL</> database system.  Readers are
!     encouraged to look at the &cite-tutorial; and the &cite-user; for
!     additional information.
     </para>
  
     <para>
Index: doc/src/sgml/charset.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/charset.sgml,v
retrieving revision 2.29
diff -c -r2.29 charset.sgml
*** doc/src/sgml/charset.sgml	21 Sep 2002 18:32:52 -0000	2.29
--- doc/src/sgml/charset.sgml	10 Nov 2002 22:25:54 -0000
***************
*** 351,357 ****
     </para>
  
      <para>
!     Multibyte support is enabled by default since PostgreSQL version 7.3.
      </para>
  
     <sect2>
--- 351,358 ----
     </para>
  
      <para>
!     Multibyte support is enabled by default since
!     <productname>PostgreSQL</> version 7.3.
      </para>
  
     <sect2>
***************
*** 574,580 ****
       encoding conversion between server and client for some
       encodings. The conversion info is stored in <literal>pg_conversion</> system
       catalog. You can create a new conversion by using <command>CREATE
!      CONVERSION</command>. PostgreSQL comes with some predefined
       conversions. They are listed in <xref
       linkend="multibyte-translation-table">.
      </para>
--- 575,581 ----
       encoding conversion between server and client for some
       encodings. The conversion info is stored in <literal>pg_conversion</> system
       catalog. You can create a new conversion by using <command>CREATE
!      CONVERSION</command>. <productname>PostgreSQL</> comes with some predefined
       conversions. They are listed in <xref
       linkend="multibyte-translation-table">.
      </para>
Index: doc/src/sgml/client-auth.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/client-auth.sgml,v
retrieving revision 1.39
diff -c -r1.39 client-auth.sgml
*** doc/src/sgml/client-auth.sgml	21 Sep 2002 18:32:52 -0000	1.39
--- doc/src/sgml/client-auth.sgml	10 Nov 2002 22:26:26 -0000
***************
*** 160,168 ****
       <term><replaceable>user</replaceable></term>
       <listitem>
        <para>
!        Specifies which PostgreSQL users this record matches. The value
!        <literal>all</literal> specifies that it matches all users.
!        Otherwise, this is the name of a specific
         <productname>PostgreSQL</productname> user. Multiple user names
         can be supplied by separating them with commas. Group names can
         be specified by preceding the group name with <literal>+</>. A
--- 160,168 ----
       <term><replaceable>user</replaceable></term>
       <listitem>
        <para>
!        Specifies which <productname>PostgreSQL</> users this record
!        matches. The value <literal>all</literal> specifies that it
!        matches all users.  Otherwise, this is the name of a specific
         <productname>PostgreSQL</productname> user. Multiple user names
         can be supplied by separating them with commas. Group names can
         be specified by preceding the group name with <literal>+</>. A
Index: doc/src/sgml/datatype.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/datatype.sgml,v
retrieving revision 1.106
diff -c -r1.106 datatype.sgml
*** doc/src/sgml/datatype.sgml	31 Oct 2002 22:18:42 -0000	1.106
--- doc/src/sgml/datatype.sgml	10 Nov 2002 22:29:22 -0000
***************
*** 1116,1131 ****
     <para>
      <acronym>SQL</acronym> string literals (input strings) must be
      preceded with two backslashes due to the fact that they must pass
!     through two parsers in the PostgreSQL backend. The first backslash
!     is interpreted as an escape character by the string-literal parser,
!     and therefore is consumed, leaving the octets that follow.
!     The remaining backslash is recognized by the <type>bytea</type> input
!     function as the prefix of a three digit octal value. For example, a string
!     literal passed to the backend as <literal>'\\001'</literal> becomes
!     <literal>'\001'</literal> after passing through the string-literal
!     parser. The <literal>'\001'</literal> is then sent to the
!     <type>bytea</type> input function, where it is converted to a single
!     octet with a decimal value of 1.
     </para>
  
     <para>
--- 1116,1132 ----
     <para>
      <acronym>SQL</acronym> string literals (input strings) must be
      preceded with two backslashes due to the fact that they must pass
!     through two parsers in the <productname>PostgreSQL</> backend. The
!     first backslash is interpreted as an escape character by the
!     string-literal parser, and therefore is consumed, leaving the
!     octets that follow.  The remaining backslash is recognized by the
!     <type>bytea</type> input function as the prefix of a three digit
!     octal value. For example, a string literal passed to the backend
!     as <literal>'\\001'</literal> becomes <literal>'\001'</literal>
!     after passing through the string-literal parser. The
!     <literal>'\001'</literal> is then sent to the <type>bytea</type>
!     input function, where it is converted to a single octet with a
!     decimal value of 1.
     </para>
  
     <para>
***************
*** 1159,1178 ****
     </para>
  
     <para>
!     Depending on the front end to PostgreSQL you use, you may have
!     additional work to do in terms of escaping and unescaping
!     <type>bytea</type> strings. For example, you may also have to escape
!     line feeds and carriage returns if your interface automatically
!     translates these. Or you may have to double up on backslashes if
!     the parser for your language or choice also treats them as an
!     escape character.
     </para>
  
      <para>
!      <type>Bytea</type> provides most of the functionality of the binary
!      string type per SQL99 section 4.3. A comparison of SQL99 Binary
!      Strings and PostgreSQL <type>bytea</type> is presented in
!      <xref linkend="datatype-binary-compat-comp">.
      </para>
  
      <table id="datatype-binary-compat-comp">
--- 1160,1179 ----
     </para>
  
     <para>
!     Depending on the front end to <productname>PostgreSQL</> you use,
!     you may have additional work to do in terms of escaping and
!     unescaping <type>bytea</type> strings. For example, you may also
!     have to escape line feeds and carriage returns if your interface
!     automatically translates these. Or you may have to double up on
!     backslashes if the parser for your language or choice also treats
!     them as an escape character.
     </para>
  
      <para>
!      <type>Bytea</type> provides most of the functionality of the
!      binary string type per SQL99 section 4.3. A comparison of SQL99
!      Binary Strings and <productname>PostgreSQL</> <type>bytea</type>
!      is presented in <xref linkend="datatype-binary-compat-comp">.
      </para>
  
      <table id="datatype-binary-compat-comp">
Index: doc/src/sgml/ddl.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ddl.sgml,v
retrieving revision 1.8
diff -c -r1.8 ddl.sgml
*** doc/src/sgml/ddl.sgml	24 Oct 2002 21:10:58 -0000	1.8
--- doc/src/sgml/ddl.sgml	10 Nov 2002 22:30:06 -0000
***************
*** 1103,1111 ****
  ALTER TABLE products ALTER COLUMN price DROP DEFAULT;
  </programlisting>
      This is equivalent to setting the default to null, at least in
!     PostgreSQL.  As a consequence, it is not an error to drop a
!     default where one hadn't been defined, because the default is
!     implicitly the null value.
     </para>
    </sect2>
  
--- 1103,1111 ----
  ALTER TABLE products ALTER COLUMN price DROP DEFAULT;
  </programlisting>
      This is equivalent to setting the default to null, at least in
!     <productname>PostgreSQL</>.  As a consequence, it is not an error
!     to drop a default where one hadn't been defined, because the
!     default is implicitly the null value.
     </para>
    </sect2>
  
***************
*** 1609,1616 ****
      standard.  Therefore, many users consider qualified names to
      really consist of
      <literal><replaceable>username</>.<replaceable>tablename</></literal>.
!     This is also supported by PostgreSQL if you create a per-user
!     schema for every user.
     </para>
  
     <para>
--- 1609,1616 ----
      standard.  Therefore, many users consider qualified names to
      really consist of
      <literal><replaceable>username</>.<replaceable>tablename</></literal>.
!     This is also supported by <productname>PostgreSQL</> if you create
!     a per-user schema for every user.
     </para>
  
     <para>
Index: doc/src/sgml/diskusage.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/diskusage.sgml,v
retrieving revision 1.6
diff -c -r1.6 diskusage.sgml
*** doc/src/sgml/diskusage.sgml	16 Oct 2002 22:06:33 -0000	1.6
--- doc/src/sgml/diskusage.sgml	10 Nov 2002 22:30:40 -0000
***************
*** 6,16 ****
   <title>Monitoring Disk Usage</title>
  
   <para>
!   This chapter discusses how to monitor the disk usage of a PostgreSQL
!   database system.  In the current release, the database administrator
!   does not have much control over the on-disk storage layout, so this
!   chapter is mostly informative and can give you some ideas how to
!   manage the disk usage with operating system tools.
   </para>
  
   <sect1 id="disk-usage">
--- 6,17 ----
   <title>Monitoring Disk Usage</title>
  
   <para>
!   This chapter discusses how to monitor the disk usage of a
!   <productname>PostgreSQL</> database system.  In the current
!   release, the database administrator does not have much control over
!   the on-disk storage layout, so this chapter is mostly informative
!   and can give you some ideas how to manage the disk usage with
!   operating system tools.
   </para>
  
   <sect1 id="disk-usage">
Index: doc/src/sgml/ecpg.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ecpg.sgml,v
retrieving revision 1.39
diff -c -r1.39 ecpg.sgml
*** doc/src/sgml/ecpg.sgml	24 Oct 2002 17:48:54 -0000	1.39
--- doc/src/sgml/ecpg.sgml	10 Nov 2002 23:07:12 -0000
***************
*** 38,63 ****
     for handling <acronym>SQL</acronym> commands from C code. First, it
     takes care of the tedious passing of information to and from
     variables in your <acronym>C</acronym> program.  Secondly, embedded
!    SQL in C is defined in the SQL standard and supported by many other
!    SQL databases.  The PostgreSQL implementation is designed to match
!    this standard as much as possible, and it is usually possible to
!    port embedded <acronym>SQL</acronym> programs written for other
     <acronym>RDBMS</acronym> to <productname>PostgreSQL</productname>
     with relative ease.
    </para>
  
    <para>
!    As indicated, programs written for the embedded SQL interface are
!    normal C programs with special code inserted to perform
!    database-related actions.  This special code always has the form
  <programlisting>
  EXEC SQL ...;
  </programlisting>
     These statements syntactically take the place of a C statement.
     Depending on the particular statement, they may appear in the
!    global context or within a function.  Embedded SQL statements
!    follow the case-sensitivity rules of normal SQL code, and not those
!    of C.
    </para>
  
    <para>
--- 38,66 ----
     for handling <acronym>SQL</acronym> commands from C code. First, it
     takes care of the tedious passing of information to and from
     variables in your <acronym>C</acronym> program.  Secondly, embedded
!    <acronym>SQL</acronym> in C is defined in the
!    <acronym>SQL</acronym> standard and supported by many other
!    <acronym>SQL</acronym> databases.  The <productname>PostgreSQL</>
!    implementation is designed to match this standard as much as
!    possible, and it is usually possible to port embedded
!    <acronym>SQL</acronym> programs written for other
     <acronym>RDBMS</acronym> to <productname>PostgreSQL</productname>
     with relative ease.
    </para>
  
    <para>
!    As indicated, programs written for the embedded
!    <acronym>SQL</acronym> interface are normal C programs with special
!    code inserted to perform database-related actions.  This special
!    code always has the form
  <programlisting>
  EXEC SQL ...;
  </programlisting>
     These statements syntactically take the place of a C statement.
     Depending on the particular statement, they may appear in the
!    global context or within a function.  Embedded
!    <acronym>SQL</acronym> statements follow the case-sensitivity rules
!    of normal <acronym>SQL</acronym> code, and not those of C.
    </para>
  
    <para>
***************
*** 748,755 ****
  
    <para>
     The preprocessor program is called <filename>ecpg</filename> and is
!    included in a normal PostgreSQL installation.  Embedded SQL
!    programs are typically named with an extension
     <filename>.pgc</filename>.  If you have a program file called
     <filename>prog1.pgc</filename>, you can preprocess it by simply
     calling
--- 751,758 ----
  
    <para>
     The preprocessor program is called <filename>ecpg</filename> and is
!    included in a normal <productname>PostgreSQL</> installation.
!    Embedded SQL programs are typically named with an extension
     <filename>.pgc</filename>.  If you have a program file called
     <filename>prog1.pgc</filename>, you can preprocess it by simply
     calling
***************
*** 768,777 ****
  cc -c prog1.c
  </programlisting>
     The generated C source files include headers files from the
!    PostgreSQL installation, so if you installed PostgreSQL in a
!    location that is not searched by default, you have to add an option
!    such as <literal>-I/usr/local/pgsql/include</literal> to the
!    compilation command line.
    </para>
  
    <para>
--- 771,781 ----
  cc -c prog1.c
  </programlisting>
     The generated C source files include headers files from the
!    <productname>PostgreSQL</> installation, so if you installed
!    <productname>PostgreSQL</> in a location that is not searched by
!    default, you have to add an option such as
!    <literal>-I/usr/local/pgsql/include</literal> to the compilation
!    command line.
    </para>
  
    <para>
Index: doc/src/sgml/features.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/features.sgml,v
retrieving revision 2.7
diff -c -r2.7 features.sgml
*** doc/src/sgml/features.sgml	21 Sep 2002 18:32:53 -0000	2.7
--- doc/src/sgml/features.sgml	10 Nov 2002 22:33:27 -0000
***************
*** 15,25 ****
    </para>
  
    <para>
!    <acronym>SQL99</acronym> defines a large set of individual
!    features rather than the ineffectively broad three levels found in
     <acronym>SQL92</acronym>. We provide a list of supported features,
!    followed by a list of the features defined in SQL99 which are not
!    yet supported in PostgreSQL.
    </para>
  
    <sect1 id="features-sql99">
--- 15,26 ----
    </para>
  
    <para>
!    <acronym>SQL99</acronym> defines a large set of individual features
!    rather than the ineffectively broad three levels found in
     <acronym>SQL92</acronym>. We provide a list of supported features,
!    followed by a list of the features defined in
!    <acronym>SQL99</acronym> which are not yet supported in
!    <productname>PostgreSQL</>.
    </para>
  
    <sect1 id="features-sql99">
Index: doc/src/sgml/info.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/info.sgml,v
retrieving revision 1.16
diff -c -r1.16 info.sgml
*** doc/src/sgml/info.sgml	24 Oct 2002 17:48:54 -0000	1.16
--- doc/src/sgml/info.sgml	10 Nov 2002 22:35:18 -0000
***************
*** 6,12 ****
   <title>Overview of Documentation Resources</title>
  
   <para>
!   The PostgreSQL documentation is organized into several books:
  
    <variablelist>
     <varlistentry>
--- 6,13 ----
   <title>Overview of Documentation Resources</title>
  
   <para>
!   The <productname>PostgreSQL</> documentation is organized into
!   several books:
  
    <variablelist>
     <varlistentry>
***************
*** 22,30 ****
      <term>&cite-user;</term>
      <listitem>
       <para>
!       Documents the SQL query language environment, including data
!       types and functions, as well as user-level performance tuning.
!       Every PostgreSQL user should read this.
       </para>
      </listitem>
     </varlistentry>
--- 23,32 ----
      <term>&cite-user;</term>
      <listitem>
       <para>
!       Documents the <acronym>SQL</acronym> query language environment,
!       including data types and functions, as well as user-level
!       performance tuning.  Every <productname>PostgreSQL</> user
!       should read this.
       </para>
      </listitem>
     </varlistentry>
***************
*** 34,41 ****
      <listitem>
       <para>
        Installation and server management information.  Everyone who
!       runs a PostgreSQL server, either for personal use or for other
!       users, needs to read this.
       </para>
      </listitem>
     </varlistentry>
--- 36,43 ----
      <listitem>
       <para>
        Installation and server management information.  Everyone who
!       runs a <productname>PostgreSQL</> server, either for personal
!       use or for other users, needs to read this.
       </para>
      </listitem>
     </varlistentry>
***************
*** 55,63 ****
      <term>&cite-reference;</term>
      <listitem>
       <para>
!       Reference pages for SQL command syntax, and client and server
!       programs.  This book is auxiliary to the User's,
!       Administrator's, and Programmer's Guides.
       </para>
      </listitem>
     </varlistentry>
--- 57,65 ----
      <term>&cite-reference;</term>
      <listitem>
       <para>
!       Reference pages for <acronym>SQL</acronym> command syntax, and
!       client and server programs.  This book is auxiliary to the
!       User's, Administrator's, and Programmer's Guides.
       </para>
      </listitem>
     </varlistentry>
Index: doc/src/sgml/installation.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/installation.sgml,v
retrieving revision 1.110
diff -c -r1.110 installation.sgml
*** doc/src/sgml/installation.sgml	5 Nov 2002 19:01:07 -0000	1.110
--- doc/src/sgml/installation.sgml	10 Nov 2002 22:37:12 -0000
***************
*** 187,194 ****
        url="http://www.python.org/doc/FAQ.html#3.30">Python FAQ
        3.30</ulink>.  On some operating systems you don't really have
        to build a shared library, but then you will have to convince
!       the PostgreSQL build system of this.  Consult the
!       <filename>Makefile</filename> in the
        <filename>src/pl/plpython</filename> directory for details.
       </para>
      </listitem>
--- 187,194 ----
        url="http://www.python.org/doc/FAQ.html#3.30">Python FAQ
        3.30</ulink>.  On some operating systems you don't really have
        to build a shared library, but then you will have to convince
!       the <productname>PostgreSQL</> build system of this.  Consult
!       the <filename>Makefile</filename> in the
        <filename>src/pl/plpython</filename> directory for details.
       </para>
      </listitem>
***************
*** 1245,1252 ****
      add <filename>/usr/local/pgsql/bin</> (or whatever you set
      <option><literal>--bindir</></> to in <xref linkend="configure">)
      into your <envar>PATH</>.  Strictly speaking, this is not
!     necessary, but it will make the use of PostgreSQL much more
!     convenient.
     </para>
  
     <para>
--- 1245,1252 ----
      add <filename>/usr/local/pgsql/bin</> (or whatever you set
      <option><literal>--bindir</></> to in <xref linkend="configure">)
      into your <envar>PATH</>.  Strictly speaking, this is not
!     necessary, but it will make the use of <productname>PostgreSQL</>
!     much more convenient.
     </para>
  
     <para>
Index: doc/src/sgml/jdbc.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/jdbc.sgml,v
retrieving revision 1.39
diff -c -r1.39 jdbc.sgml
*** doc/src/sgml/jdbc.sgml	1 Oct 2002 04:09:13 -0000	1.39
--- doc/src/sgml/jdbc.sgml	10 Nov 2002 22:37:51 -0000
***************
*** 51,66 ****
     </para>
  
     <para>
!     Alternatively you can build the driver from source, but you
!     should only need to do this if you are making changes to the
!     source code.  For details, refer to the PostgreSQL installation
      instructions.  After installation, the driver should be found in
      <filename><replaceable>PREFIX</>/share/java/postgresql.jar</filename>.
      The resulting driver will be built for the version of Java you are
!     running.  If you build with a 1.1 <acronym>JDK</> you will build a version
!     that supports the JDBC 1 specification, if you build with a Java 2
!     <acronym>JDK</> (e.g., <acronym>JDK</> 1.2 or <acronym>JDK</> 1.3) you will build a version that
!     supports the JDBC 2 specification.
     </para>
    </sect2>
  
--- 51,67 ----
     </para>
  
     <para>
!     Alternatively you can build the driver from source, but you should
!     only need to do this if you are making changes to the source code.
!     For details, refer to the <productname>PostgreSQL</> installation
      instructions.  After installation, the driver should be found in
      <filename><replaceable>PREFIX</>/share/java/postgresql.jar</filename>.
      The resulting driver will be built for the version of Java you are
!     running.  If you build with a 1.1 <acronym>JDK</> you will build a
!     version that supports the JDBC 1 specification, if you build with
!     a Java 2 <acronym>JDK</> (e.g., <acronym>JDK</> 1.2 or
!     <acronym>JDK</> 1.3) you will build a version that supports the
!     JDBC 2 specification.
     </para>
    </sect2>
  
Index: doc/src/sgml/libpgtcl.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/libpgtcl.sgml,v
retrieving revision 1.32
diff -c -r1.32 libpgtcl.sgml
*** doc/src/sgml/libpgtcl.sgml	8 Nov 2002 04:56:40 -0000	1.32
--- doc/src/sgml/libpgtcl.sgml	10 Nov 2002 22:38:17 -0000
***************
*** 1112,1118 ****
  <TITLE>Description
  </TITLE>
  <PARA>
! <FUNCTION>pg_execute</FUNCTION> submits a query to the PostgreSQL backend.
  </PARA>
  <PARA>
  If the query is not a SELECT statement, the query is executed and the
--- 1112,1119 ----
  <TITLE>Description
  </TITLE>
  <PARA>
! <FUNCTION>pg_execute</FUNCTION> submits a query to the
! <PRODUCTNAME>PostgreSQL</> backend.
  </PARA>
  <PARA>
  If the query is not a SELECT statement, the query is executed and the
Index: doc/src/sgml/libpq.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/libpq.sgml,v
retrieving revision 1.100
diff -c -r1.100 libpq.sgml
*** doc/src/sgml/libpq.sgml	10 Nov 2002 00:14:22 -0000	1.100
--- doc/src/sgml/libpq.sgml	10 Nov 2002 22:38:53 -0000
***************
*** 957,968 ****
  
    <para>
     <function>PQescapeBytea</> returns an escaped version of the
!    <parameter>from</parameter> parameter binary string, to a caller-provided
!     buffer. The return string has all special characters replaced
!    so that they can be properly processed by the PostgreSQL string literal
!    parser, and the <type>bytea</type> input function. A terminating zero
!    byte is also added.  The single quotes that must surround
!    PostgreSQL string literals are not part of the result string.
    </para>
  
    <para>
--- 957,970 ----
  
    <para>
     <function>PQescapeBytea</> returns an escaped version of the
!    <parameter>from</parameter> parameter binary string, to a
!    caller-provided buffer. The return string has all special
!    characters replaced so that they can be properly processed by the
!    <productname>PostgreSQL</> string literal parser, and the
!    <type>bytea</type> input function. A terminating zero byte is also
!    added.  The single quotes that must surround
!    <productname>PostgreSQL</> string literals are not part of the
!    result string.
    </para>
  
    <para>
Index: doc/src/sgml/manage-ag.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/manage-ag.sgml,v
retrieving revision 2.22
diff -c -r2.22 manage-ag.sgml
*** doc/src/sgml/manage-ag.sgml	24 Oct 2002 17:48:54 -0000	2.22
--- doc/src/sgml/manage-ag.sgml	10 Nov 2002 22:40:47 -0000
***************
*** 8,32 ****
   <indexterm zone="managing-databases"><primary>database</></>
  
   <para>
!   Every instance of a running PostgreSQL server manages one or more
!   databases.  Databases are therefore the topmost hierarchical level
!   for organizing SQL objects (<quote>database objects</quote>).  This
!   chapter describes the properties of databases, and how to create,
!   manage, and destroy them.
   </para>
  
   <sect1>
    <title>Overview</title>
  
    <para>
!    A database is a named collection of SQL objects (<quote>database
!    objects</quote>).  Generally, every database object (tables,
!    functions, etc.) belongs to one and only one database.  (But there
!    are a few system catalogs, for example <literal>pg_database</>,
!    that belong to a whole installation and are accessible from each
!    database within the installation.)  More accurately, a database is
!    a collection of schemas and the schemas contain the tables,
!    functions, etc.  So the full hierarchy is:
     server-database-schema-table (or something else instead of a
     table).
    </para>
--- 8,33 ----
   <indexterm zone="managing-databases"><primary>database</></>
  
   <para>
!   Every instance of a running <productname>PostgreSQL</> server
!   manages one or more databases.  Databases are therefore the topmost
!   hierarchical level for organizing <acronym>SQL</acronym> objects
!   (<quote>database objects</quote>).  This chapter describes the
!   properties of databases, and how to create, manage, and destroy
!   them.
   </para>
  
   <sect1>
    <title>Overview</title>
  
    <para>
!    A database is a named collection of <acronym>SQL</acronym> objects
!    (<quote>database objects</quote>).  Generally, every database
!    object (tables, functions, etc.) belongs to one and only one
!    database.  (But there are a few system catalogs, for example
!    <literal>pg_database</>, that belong to a whole installation and
!    are accessible from each database within the installation.)  More
!    accurately, a database is a collection of schemas and the schemas
!    contain the tables, functions, etc.  So the full hierarchy is:
     server-database-schema-table (or something else instead of a
     table).
    </para>
***************
*** 41,53 ****
     connection.  Schemas are a purely logical structure and who can
     access what is managed by the privilege system.  Databases are
     physically separated and access control is managed at the
!    connection level.  If one PostgreSQL server instance is to house
!    projects or users that should be separate and for the most part
!    unaware of each other, it is therefore recommendable to put them
!    into separate databases.  If the projects or users are interrelated
!    and should be able to use each other's resources they should be put
!    in the same databases but possibly into separate schemas.  More
!    information about managing schemas is in the &cite-user;.
    </para>
  
    <note>
--- 42,55 ----
     connection.  Schemas are a purely logical structure and who can
     access what is managed by the privilege system.  Databases are
     physically separated and access control is managed at the
!    connection level.  If one <productname>PostgreSQL</> server
!    instance is to house projects or users that should be separate and
!    for the most part unaware of each other, it is therefore
!    recommendable to put them into separate databases.  If the projects
!    or users are interrelated and should be able to use each other's
!    resources they should be put in the same databases but possibly
!    into separate schemas.  More information about managing schemas is
!    in the &cite-user;.
    </para>
  
    <note>
***************
*** 73,83 ****
  <synopsis>
  CREATE DATABASE <replaceable>name</>
  </synopsis>
!    where <replaceable>name</> follows the usual rules for SQL identifiers.
!    The current user automatically becomes
!    the owner of the new database. It is the privilege of the owner of
!    a database to remove it later on (which also removes all the
!    objects in it, even if they have a different owner).
    </para>
  
    <para>
--- 75,85 ----
  <synopsis>
  CREATE DATABASE <replaceable>name</>
  </synopsis>
!    where <replaceable>name</> follows the usual rules for
!    <acronym>SQL</acronym> identifiers.  The current user automatically
!    becomes the owner of the new database. It is the privilege of the
!    owner of a database to remove it later on (which also removes all
!    the objects in it, even if they have a different owner).
    </para>
  
    <para>
***************
*** 262,271 ****
    <title>Database Configuration</title>
  
    <para>
!    Recall from <xref linkend="runtime-config"> that the PostgreSQL
!    server provides a large number of run-time configuration variables.
!    You can set database-specific default values for many of these
!    settings.
    </para>
  
    <para>
--- 264,273 ----
    <title>Database Configuration</title>
  
    <para>
!    Recall from <xref linkend="runtime-config"> that the
!    <productname>PostgreSQL</> server provides a large number of
!    run-time configuration variables.  You can set database-specific
!    default values for many of these settings.
    </para>
  
    <para>
Index: doc/src/sgml/programmer.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/programmer.sgml,v
retrieving revision 1.43
diff -c -r1.43 programmer.sgml
*** doc/src/sgml/programmer.sgml	24 Oct 2002 17:48:54 -0000	1.43
--- doc/src/sgml/programmer.sgml	10 Nov 2002 22:41:52 -0000
***************
*** 24,41 ****
     <title>What's In This Book</title>
  
     <para>
!     This book is for PostgreSQL application programmers.  It is divided into three parts.
     </para>
  
     <para>
      The first part of this book describes the client programming
!     interfaces distributed with PostgreSQL.  Each of these chapters
!     can be read independently.  Note that there are many other
!     programming interfaces for client programs that are distributed
!     separately and contain their own documentation.  Readers of the
!     first part should be familiar with using SQL commands to
!     manipulate and query the database (see the &cite-user;) and of
!     course with the programming language that the interface uses.
     </para>
  
     <para>
--- 24,43 ----
     <title>What's In This Book</title>
  
     <para>
!     This book is for <productname>PostgreSQL</> application
!     programmers.  It is divided into three parts.
     </para>
  
     <para>
      The first part of this book describes the client programming
!     interfaces distributed with <productname>PostgreSQL</>.  Each of
!     these chapters can be read independently.  Note that there are
!     many other programming interfaces for client programs that are
!     distributed separately and contain their own documentation.
!     Readers of the first part should be familiar with using
!     <acronym>SQL</acronym> commands to manipulate and query the
!     database (see the &cite-user;) and of course with the programming
!     language that the interface uses.
     </para>
  
     <para>
***************
*** 43,49 ****
      functionality with user-defined functions, data types, triggers,
      etc.  These are advanced topics which should probably be
      approached only after all the other user documentation about
!     PostgreSQL has been understood.
     </para>
  
     <para>
--- 45,51 ----
      functionality with user-defined functions, data types, triggers,
      etc.  These are advanced topics which should probably be
      approached only after all the other user documentation about
!     <productname>PostgreSQL</> has been understood.
     </para>
  
     <para>
Index: doc/src/sgml/user.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/user.sgml,v
retrieving revision 1.33
diff -c -r1.33 user.sgml
*** doc/src/sgml/user.sgml	24 Oct 2002 17:48:54 -0000	1.33
--- doc/src/sgml/user.sgml	10 Nov 2002 22:51:39 -0000
***************
*** 23,35 ****
     <title>What's In This Book</title>
  
     <para>
!     This book describes the use of the SQL language in PostgreSQL.  We
!     start with describing the general syntax of SQL, then explain how
!     to create the structures to hold data, how to populate the
!     database, and how to query it.  The middle part lists the
!     available data types and functions for use in SQL data commands.
!     The rest of the book treats several aspects that are important for
!     tuning a database for optimial performance.
     </para>
  
     <para>
--- 23,36 ----
     <title>What's In This Book</title>
  
     <para>
!     This book describes the use of the <acronym>SQL</acronym> language
!     in <productna,e>PostgreSQL</>.  We start with describing the
!     general syntax of <acronym>SQL</acronym>, then explain how to
!     create the structures to hold data, how to populate the database,
!     and how to query it.  The middle part lists the available data
!     types and functions for use in <acronym>SQL</acronym> data
!     commands.  The rest of the book treats several aspects that are
!     important for tuning a database for optimial performance.
     </para>
  
     <para>
***************
*** 44,53 ****
     </para>
  
     <para>
!     Readers of this book should know how to connect to a PostgreSQL
!     database and issue SQL commands.  Readers that are unfamiliar with
!     these issues are encouraged to read the &cite-tutorial; first.  SQL
!     commands are typically entered using the PostgreSQL interactive
      terminal <application>psql</application>, but other programs that
      have similar functionality can be used as well.
     </para>
--- 45,54 ----
     </para>
  
     <para>
!     Readers of this book should know how to connect to a <productname>PostgreSQL</>
!     database and issue <acronym>SQL</acronym> commands.  Readers that are unfamiliar with
!     these issues are encouraged to read the &cite-tutorial; first.  <acronym>SQL</acronym>
!     commands are typically entered using the <productname>PostgreSQL</> interactive
      terminal <application>psql</application>, but other programs that
      have similar functionality can be used as well.
     </para>
Index: doc/src/sgml/ref/create_cast.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/create_cast.sgml,v
retrieving revision 1.6
diff -c -r1.6 create_cast.sgml
*** doc/src/sgml/ref/create_cast.sgml	4 Oct 2002 22:08:44 -0000	1.6
--- doc/src/sgml/ref/create_cast.sgml	10 Nov 2002 22:42:38 -0000
***************
*** 196,209 ****
    </para>
  
    <para>
!    Prior to PostgreSQL 7.3, every function that had the same name as a
!    data type, returned that data type, and took one argument of a
!    different type was automatically a cast function.  This convention has
!    been abandoned in face of the introduction of schemas and to be
!    able to represent binary compatible casts in the catalogs.  (The built-in
!    cast functions
!    still follow this naming scheme, but they have to be shown as
!    casts in <literal>pg_cast</> now.)
    </para>
   </refsect1>
  
--- 196,209 ----
    </para>
  
    <para>
!    Prior to <productname>PostgreSQL</> 7.3, every function that had
!    the same name as a data type, returned that data type, and took one
!    argument of a different type was automatically a cast function.
!    This convention has been abandoned in face of the introduction of
!    schemas and to be able to represent binary compatible casts in the
!    catalogs.  (The built-in cast functions still follow this naming
!    scheme, but they have to be shown as casts in <literal>pg_cast</>
!    now.)
    </para>
   </refsect1>
  
Index: doc/src/sgml/ref/ecpg-ref.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/ecpg-ref.sgml,v
retrieving revision 1.22
diff -c -r1.22 ecpg-ref.sgml
*** doc/src/sgml/ref/ecpg-ref.sgml	24 Oct 2002 17:48:54 -0000	1.22
--- doc/src/sgml/ref/ecpg-ref.sgml	10 Nov 2002 22:52:02 -0000
***************
*** 157,165 ****
    <para>
     When compiling the preprocessed C code files, the compiler needs to
     be able to find the <application>ECPG</> header files in the
!    PostgreSQL include directory.  Therefore, one might have to use the
!    <option>-I</> option when invoking the compiler (e.g.,
!    <literal>-I/usr/local/pgsql/include</literal>).
    </para>
  
    <para>
--- 157,165 ----
    <para>
     When compiling the preprocessed C code files, the compiler needs to
     be able to find the <application>ECPG</> header files in the
!    <productname>PostgreSQL</> include directory.  Therefore, one might
!    have to use the <option>-I</> option when invoking the compiler
!    (e.g., <literal>-I/usr/local/pgsql/include</literal>).
    </para>
  
    <para>
Index: doc/src/sgml/ref/load.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/load.sgml,v
retrieving revision 1.12
diff -c -r1.12 load.sgml
*** doc/src/sgml/ref/load.sgml	20 Jan 2002 22:19:57 -0000	1.12
--- doc/src/sgml/ref/load.sgml	10 Nov 2002 22:44:42 -0000
***************
*** 23,35 ****
    <title>Description</title>
  
    <para>
!    Loads a shared library file into the PostgreSQL backend's address
!    space.  If the file had been loaded previously, it is first
!    unloaded.  This command is primarily useful to unload and reload a
!    shared library file that has been changed since the backend first
!    loaded it.  To make use of the
!    shared library, function(s) in it need to be declared using the <xref
!    linkend="sql-createfunction" endterm="sql-createfunction-title"> command.
    </para>
  
    <para>
--- 23,36 ----
    <title>Description</title>
  
    <para>
!    Loads a shared library file into the <productname>PostgreSQL</>
!    backend's address space.  If the file had been loaded previously,
!    it is first unloaded.  This command is primarily useful to unload
!    and reload a shared library file that has been changed since the
!    backend first loaded it.  To make use of the shared library,
!    function(s) in it need to be declared using the <xref
!    linkend="sql-createfunction" endterm="sql-createfunction-title">
!    command.
    </para>
  
    <para>
Index: doc/src/sgml/ref/pg_config-ref.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/pg_config-ref.sgml,v
retrieving revision 1.11
diff -c -r1.11 pg_config-ref.sgml
*** doc/src/sgml/ref/pg_config-ref.sgml	11 Oct 2002 23:03:48 -0000	1.11
--- doc/src/sgml/ref/pg_config-ref.sgml	10 Nov 2002 22:45:51 -0000
***************
*** 131,137 ****
  
    <para>
     The option <option>--includedir-server</option> is new in
!    PostgreSQL 7.2.  In prior releases, the server include files were
     installed in the same location as the client headers, which could
     be queried with the <option>--includedir</option>.  To make your
     package handle both cases, try the newer option first and test the
--- 131,137 ----
  
    <para>
     The option <option>--includedir-server</option> is new in
!    <productname>PostgreSQL</> 7.2.  In prior releases, the server include files were
     installed in the same location as the client headers, which could
     be queried with the <option>--includedir</option>.  To make your
     package handle both cases, try the newer option first and test the
***************
*** 139,145 ****
    </para>
  
    <para>
!    In releases prior to PostgreSQL 7.1, before the
     <command>pg_config</command> came to be, a method for finding the
     equivalent configuration information did not exist.
    </para>
--- 139,145 ----
    </para>
  
    <para>
!    In releases prior to <productname>PostgreSQL</> 7.1, before the
     <command>pg_config</command> came to be, a method for finding the
     equivalent configuration information did not exist.
    </para>
***************
*** 150,156 ****
    <title>History</title>
  
    <para>
!    The <command>pg_config</command> utility first appeared in PostgreSQL 7.1.
    </para>
   </refsect1>
  
--- 150,157 ----
    <title>History</title>
  
    <para>
!    The <command>pg_config</command> utility first appeared in
!    <productname>PostgreSQL</> 7.1.
    </para>
   </refsect1>
  
Index: doc/src/sgml/ref/pg_dump.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/pg_dump.sgml,v
retrieving revision 1.52
diff -c -r1.52 pg_dump.sgml
*** doc/src/sgml/ref/pg_dump.sgml	11 Oct 2002 23:03:48 -0000	1.52
--- doc/src/sgml/ref/pg_dump.sgml	10 Nov 2002 22:46:48 -0000
***************
*** 274,284 ****
  
         <para>
          <application>pg_dump</application> can handle databases from
!         previous releases of PostgreSQL, but very old versions are not
!         supported anymore (currently prior to 7.0).  Use this option
!         if you need to override the version check (and if
!         <application>pg_dump</application> then fails, don't say you
!         weren't warned).
         </para>
        </listitem>
       </varlistentry>
--- 274,284 ----
  
         <para>
          <application>pg_dump</application> can handle databases from
!         previous releases of <productname>PostgreSQL</>, but very old
!         versions are not supported anymore (currently prior to 7.0).
!         Use this option if you need to override the version check (and
!         if <application>pg_dump</application> then fails, don't say
!         you weren't warned).
         </para>
        </listitem>
       </varlistentry>
***************
*** 289,295 ****
        <listitem>
         <para>
  	Dump object identifiers (<acronym>OID</acronym>s) for every
! 	table.  Use this option if your application references the OID
  	columns in some way (e.g., in a foreign key constraint).
  	Otherwise, this option should not be used.
         </para>
--- 289,295 ----
        <listitem>
         <para>
  	Dump object identifiers (<acronym>OID</acronym>s) for every
! 	table.  Use this option if your application references the <acronym>OID</>
  	columns in some way (e.g., in a foreign key constraint).
  	Otherwise, this option should not be used.
         </para>
Index: doc/src/sgml/ref/pg_dumpall.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/pg_dumpall.sgml,v
retrieving revision 1.34
diff -c -r1.34 pg_dumpall.sgml
*** doc/src/sgml/ref/pg_dumpall.sgml	7 Sep 2002 16:14:33 -0000	1.34
--- doc/src/sgml/ref/pg_dumpall.sgml	10 Nov 2002 22:47:36 -0000
***************
*** 27,39 ****
  
    <para>
     <application>pg_dumpall</application> is a utility for writing out
!    (<quote>dumping</quote>) all PostgreSQL databases of a cluster into
!    one script file.  The script file contains SQL commands that can be
!    used as input to <xref linkend="app-psql">
!    to restore the databases.  It does this by calling <xref
!    linkend="app-pgdump"> for each database
!    in a cluster.  <application>pg_dumpall</application> also dumps
!    global objects that are common to all databases.
     (<application>pg_dump</application> does not save these objects.)
     This currently includes the information about database users and
     groups.
--- 27,39 ----
  
    <para>
     <application>pg_dumpall</application> is a utility for writing out
!    (<quote>dumping</quote>) all <productname>PostgreSQL</> databases
!    of a cluster into one script file.  The script file contains
!    <acronym>SQL</acronym> commands that can be used as input to <xref
!    linkend="app-psql"> to restore the databases.  It does this by
!    calling <xref linkend="app-pgdump"> for each database in a cluster.
!    <application>pg_dumpall</application> also dumps global objects
!    that are common to all databases.
     (<application>pg_dump</application> does not save these objects.)
     This currently includes the information about database users and
     groups.
***************
*** 139,149 ****
  
         <para>
          <application>pg_dumpall</application> can handle databases
!         from previous releases of PostgreSQL, but very old versions
!         are not supported anymore (currently prior to 7.0).  Use this
!         option if you need to override the version check (and if
!         <application>pg_dumpall</application> then fails, don't say
!         you weren't warned).
         </para>
        </listitem>
       </varlistentry>
--- 139,149 ----
  
         <para>
          <application>pg_dumpall</application> can handle databases
!         from previous releases of <productname>PostgreSQL</>, but very
!         old versions are not supported anymore (currently prior to
!         7.0).  Use this option if you need to override the version
!         check (and if <application>pg_dumpall</application> then
!         fails, don't say you weren't warned).
         </para>
        </listitem>
       </varlistentry>
Index: doc/src/sgml/ref/pg_restore.sgml
===================================================================
RCS file: /var/lib/cvs/pgsql-server/doc/src/sgml/ref/pg_restore.sgml,v
retrieving revision 1.31
diff -c -r1.31 pg_restore.sgml
*** doc/src/sgml/ref/pg_restore.sgml	11 Oct 2002 23:03:48 -0000	1.31
--- doc/src/sgml/ref/pg_restore.sgml	10 Nov 2002 22:50:10 -0000
***************
*** 417,427 ****
         </para>
  
         <para>
!         Presently, the commands emitted for <option>--disable-triggers</>
! 	must be done as superuser.  So, you should also specify
! 	a superuser name with <option>-S</>, or preferably specify
! 	<option>--use-set-session-authorization</> and run
! 	<application>pg_restore</application> as a PostgreSQL superuser.
         </para>
        </listitem>
       </varlistentry>
--- 417,428 ----
         </para>
  
         <para>
!         Presently, the commands emitted for
! 	<option>--disable-triggers</> must be done as superuser.  So, you
! 	should also specify a superuser name with <option>-S</>, or
! 	preferably specify <option>--use-set-session-authorization</> and
! 	run <application>pg_restore</application> as a
! 	<productname>PostgreSQL</> superuser.
         </para>
        </listitem>
       </varlistentry>
***************
*** 522,533 ****
      <msgexplan>
         <para>
  	<application>pg_restore</application> could not attach to the
!         PostgreSQL server
! 	process on the specified host and port.  If you see this message,
! 	ensure that the server
! 	is running on the proper host and that you have specified the proper
! 	port.  If your site uses an authentication system, ensure that you
! 	have obtained the required authentication credentials.
         </para>
      </msgexplan>
     </msgentry>
--- 523,534 ----
      <msgexplan>
         <para>
  	<application>pg_restore</application> could not attach to the
!         <productname>PostgreSQL</> server process on the specified
!         host and port.  If you see this message, ensure that the
!         server is running on the proper host and that you have
!         specified the proper port.  If your site uses an
!         authentication system, ensure that you have obtained the
!         required authentication credentials.
         </para>
      </msgexplan>
     </msgentry>
***************
*** 537,543 ****
      <para>
       When a direct database connection is specified using the -d
       option, <application>pg_restore</application> internally executes
!      SQL statements. If you have problems running
       <application>pg_restore</application>, make sure you are able to select
       information from the database using, for example,
       <application>psql</application>.
--- 538,544 ----
      <para>
       When a direct database connection is specified using the -d
       option, <application>pg_restore</application> internally executes
!      <acronym>SQL</acronym> statements. If you have problems running
       <application>pg_restore</application>, make sure you are able to select
       information from the database using, for example,
       <application>psql</application>.