Re: pg_dump new -n flag - Mailing list pgsql-hackers

From Thomas G. Lockhart
Subject Re: pg_dump new -n flag
Date
Msg-id 3617FDA1.57386F2@alumni.caltech.edu
Whole thread Raw
Responses Re: pg_dump new -n flag  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
> Did you update the man pages or docs?  I don't see the man page
> changed. Do you want me to do it?

Funny you should ask...

I'm just in the process of converting all of the "utilities" man pages
to sgml. For this release, we should keep the man pages as-is, but we
will have equivalent info in hardcopy and html.

So, I haven't updated the man page yet, but I'll do that. I did update
the usage printout from pg_dump itself.

And, can we be sure to update both sgml and man pages from here to
release to keep them in sync? I should be able to commit most sgml
sources for the utilities this evening; on my list of "must-haves" just
pg_dump, pg_dumpall, and vacuum are left to do.

btw, is "-n" an acceptable choice for the flag? I'd be happy with
anything, but decided that "-q" probably shouldn't be used since many
programs use it to mean "quiet". So -n for "No quotes" is what I chose
instead...

                     - Tom

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: TCL_ARRAYS code in libpgtcl is pretty seriously broken
Next
From: "Marc G. Fournier"
Date:
Subject: Re: [HACKERS] Re: CIDR/IP types. Was: [GENERAL] big numbers