Re: Should we put command options in alphabetical order in the doc? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Should we put command options in alphabetical order in the doc?
Date
Msg-id 3024596.1681940741@sss.pgh.pa.us
Whole thread Raw
In response to Re: Should we put command options in alphabetical order in the doc?  (Melanie Plageman <melanieplageman@gmail.com>)
List pgsql-hackers
Melanie Plageman <melanieplageman@gmail.com> writes:
> I do think we should consider deprecating and dropping documentation of
> the options that are supported without parentheses (relevant to commands
> like ANALYZE, CLUSTER, VACUUM, and others). It is fine if we keep the
> code to make ANALYZE VERBOSE work, but I don't think it is useful to
> keep that documented. That is not a concern of this patch, however.

I doubt it's a great idea to de-document syntax that's still allowed
and will still be widely used for years to come; that just promotes
confusion.  However, we could do something similar to what we did
for COPY years ago, and move the un-parenthesized syntax to the
"Compatibility" section.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: [PATCH] Allow Postgres to pick an unused port to listen
Next
From: David Rowley
Date:
Subject: Re: Incremental sort for access method with ordered scan support (amcanorderbyop)