public inbox for [email protected]
help / color / mirror / Atom feedFrom: Alvaro Herrera <[email protected]>
To: Peter Geoghegan <[email protected]>
Cc: David Rowley <[email protected]>
Cc: PostgreSQL Developers <[email protected]>
Subject: Re: Should we put command options in alphabetical order in the doc?
Date: Wed, 19 Apr 2023 10:47:47 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAH2-WzmcG1V14d=F7YF0gwEYh0xQE0BVvsO7SwDB9sgx2pBAYA@mail.gmail.com>
On 2023-Apr-18, Peter Geoghegan wrote:
> While I'm certain that nobody will agree with me on every little
> detail, I have to imagine that most would find my preferred ordering
> quite understandable and unsurprising, at a high level -- this is not
> a hopelessly idiosyncratic ranking, that could just as easily have
> been generated by a PRNG. People may not easily agree that "apples are
> more important than oranges, or vice-versa", but what does it matter?
> I've really only put each option into buckets of items with *roughly*
> the same importance. All of the details beyond that don't matter to
> me, at all.
I agree with you that roughly bucketing items is a good approach.
Within each bucket we can then sort alphabetically.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"If you have nothing to say, maybe you need just the right tool to help you
not say it." (New York Times, about Microsoft PowerPoint)
view thread (10+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Should we put command options in alphabetical order in the doc?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox