Thread: pg_dump

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>

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

Got it. Thanks.

Peter E and other doc'ers:

While there, I noticed that there were some embedded ^M's at the end of
some lines of text. I have a utility to scrub that cruft off of the end
of lines (it scrubs any non-printable character and any whitespace) and
have run it on all of the ref/ files; some had ^M's and others had some
other kind of whitespace stripped out. Most files got touched.

I'd like to commit these at some point, but perhaps I should wait until
freezing the docs? Which btw is Real Soon Now, since scrappy may be
close to declaring the release date.

Comments?

                      - Thomas

Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
> While there, I noticed that there were some embedded ^M's at the end of
> some lines of text.

Yeah, I'd griped about that a month or so back, but didn't get around to
doing something about it.

> I have a utility to scrub that cruft off of the end
> of lines (it scrubs any non-printable character and any whitespace) and
> have run it on all of the ref/ files; some had ^M's and others had some
> other kind of whitespace stripped out. Most files got touched.

> I'd like to commit these at some point, but perhaps I should wait until
> freezing the docs?

I'd say commit now, else you'll have to redo the work later.  I think we
are still doing minor changes to the docs, but probably nothing major...

            regards, tom lane