Re: Multiple --table options for other commands - Mailing list pgsql-hackers

From Josh Kupershmidt
Subject Re: Multiple --table options for other commands
Date
Msg-id CAK3UJRGkMO+W10sfVYoD-31qKm5WqByqiNxLAyeyDre4f0-QXg@mail.gmail.com
Whole thread Raw
In response to Re: Multiple --table options for other commands  ("Karl O. Pinc" <kop@meme.com>)
Responses Re: Multiple --table options for other commands
List pgsql-hackers
On Wed, Dec 12, 2012 at 8:14 AM, Karl O. Pinc <kop@meme.com> wrote:
> On 12/11/2012 10:25:43 PM, Josh Kupershmidt wrote:
>> On Tue, Dec 11, 2012 at 11:46 AM, Karl O. Pinc <kop@meme.com> wrote:
>> >> I believe you need ellipses behind --table in the syntax summaries
>> >> of the command reference docs.
>>
>> Hrm, I was following pg_dump's lead here for the .sgml docs, and
>> didn't see anywhere that pg_dump makes the multiple --table syntax
>> explicit other than in the explanatory text underneath the option.
>
> Yes.  I see.  I didn't look at all the command's reference pages
> but did happen to look at clusterdb, which does have --table
> in the syntax summary.  I just checked and you need to fix
> clusterdb, reindexdb, and vacuumdb.

OK, I made some changes to the command synopses for these three
commands. For some reason, reindexdb.sgml was slightly different from
the other two, in that the --table and --index bits were underneath a
<group> node instead of <arg>. I've changed that one to be like the
other two, and made them all have:
     <arg choice="opt" rep="repeat">

to include the ellipses after the table -- I hope that matches what
you had in mind.

Josh

Attachment

pgsql-hackers by date:

Previous
From: Pavan Deolasee
Date:
Subject: Re: [PERFORM] encouraging index-only scans
Next
From: "Karl O. Pinc"
Date:
Subject: Re: Multiple --table options for other commands