From: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
---|---|
To: | "Karl O(dot) Pinc" <kop(at)meme(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Multiple --table options for other commands |
Date: | 2012-12-13 05:04:53 |
Message-ID: | CAK3UJRGkMO+W10sfVYoD-31qKm5WqByqiNxLAyeyDre4f0-QXg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 12, 2012 at 8:14 AM, Karl O. Pinc <kop(at)meme(dot)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(at)meme(dot)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 | Content-Type | Size |
---|---|---|
multiple_tables.v3.diff | application/octet-stream | 28.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Karl O. Pinc | 2012-12-13 06:35:14 | Re: Multiple --table options for other commands |
Previous Message | Pavan Deolasee | 2012-12-13 04:48:48 | Re: [PERFORM] encouraging index-only scans |