Re: Ordering in guc.c vs. config.sgml vs. postgresql.sample.conf

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Ordering in guc.c vs. config.sgml vs. postgresql.sample.conf
Date: 2016-04-25 16:57:50
Message-ID: CA+Tgmob5K+7tt_NGe496jUOZHj9hXO=31OoipLPdog2BuUyt4w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 25, 2016 at 6:29 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> guc.c might be better to just stick to alphabetical per group. (Which we
> also don't do today, of course, but it could be a better way to do it there)

For myself, I would rather have guc.c in the order that it's in.
Related options tend to be next to each other, and being able to look
up and down to see that they are all consistent has value for me. If
we put them in alphabetical order, that's likely to be less true. And
realistically, anybody who is looking for a particular setting is just
going to ask their editor to find it for them, so there's not a lot of
value in alpha order that I can see.

However, if I lose this argument, I will not cry into my beer. Just
throwing out my $0.02.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-04-25 17:03:20 Re: EXPLAIN VERBOSE with parallel Aggregate
Previous Message Robert Haas 2016-04-25 16:38:36 Re: [BUGS] Breakage with VACUUM ANALYSE + partitions