Received: from ns1.greatbridge.com (ns1.greatbridge.com [216.54.52.10])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f1QMEtx39096
	for <pgsql-docs@postgresql.org>; Mon, 26 Feb 2001 17:14:55 -0500 (EST)
	(envelope-from pierce@greatbridge.com)
Received: (from daemon@localhost)
	by ns1.greatbridge.com (8.9.3/8.9.3) id RAA22065;
	Mon, 26 Feb 2001 17:19:41 -0500
Received: from UNKNOWN(216.54.52.226), claiming to be "greatbridge.com"
	via SMTP by ns1, id smtpdphdhQp; Mon Feb 26 17:19:38 2001
Message-ID: <3A9AD604.85EDD353@greatbridge.com>
Date: Mon, 26 Feb 2001 17:17:40 -0500
From: Pierce Tyler <pierce@greatbridge.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: lockhart@fourpalms.org
CC: pgsql-docs@postgresql.org
Subject: pg_dump
Content-Type: multipart/mixed; boundary="------------57FB3E8090F4D1B10D59445B"
X-Archive-Number: 200102/160
X-Sequence-Number: 420

This is a multi-part message in MIME format.
--------------57FB3E8090F4D1B10D59445B
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Noticed a couple of typos in the pg_dump docs (Reference Guide).
Suggested corrections attached.

Pierce
-- 
--------------------------------------------------------------
Pierce Tyler                    | e: pierce@greatbridge.com
Technical Writer                | p: (757)233-5544
Great Bridge, LLC               | w: www.greatbridge.com
                                     www.greatbridge.org
--------------57FB3E8090F4D1B10D59445B
Content-Type: text/plain; charset=us-ascii; name="pg_dump.sgml.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="pg_dump.sgml.diff"

*** ref-symlink/pg_dump.sgml	Mon Dec 25 18:15:26 2000
--- pg_dump.sgml	Mon Feb 26 16:49:38 2001
***************
*** 475,481 ****
    <para>
     When used with one of the alternate file formats and combined with 
     <APPLICATION>pg_restore</APPLICATION>, it provides a flexible archival 
!    and trasfer mechanism. <APPLICATION>pg_dump</APPLICATION> can be used 
     to backup an entire database, then <APPLICATION>pg_restore</APPLICATION> 
     can be used to examine the archive and/or select which parts of the 
     database are to be restored.
--- 475,481 ----
    <para>
     When used with one of the alternate file formats and combined with 
     <APPLICATION>pg_restore</APPLICATION>, it provides a flexible archival 
!    and transfer mechanism. <APPLICATION>pg_dump</APPLICATION> can be used 
     to backup an entire database, then <APPLICATION>pg_restore</APPLICATION> 
     can be used to examine the archive and/or select which parts of the 
     database are to be restored.
***************
*** 513,519 ****
       <para>
        When dumping a single table or as plain text, <application>pg_dump</application> 
        does not handle large objects. Large objects must be dumped in their
!       entirity using one of the binary archive formats.
       </para>
      </listitem>
  
--- 513,519 ----
       <para>
        When dumping a single table or as plain text, <application>pg_dump</application> 
        does not handle large objects. Large objects must be dumped in their
!       entirety using one of the binary archive formats.
       </para>
      </listitem>
  

--------------57FB3E8090F4D1B10D59445B--