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*** 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>
