From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Kupershmidt <schmiddy@gmail.com>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: Confusing section of 'Setting Parameters'
Date: Thu, 10 May 2012 23:05:32 -0400
Message-ID: <20001.1336705532@sss.pgh.pa.us> (raw)
In-Reply-To: <CAK3UJRHyjfQmrEa4sONcmfi=Ah0-2Ncg-eVMoRnu6OYJzQ31OQ@mail.gmail.com>
References: <CAK3UJRHyjfQmrEa4sONcmfi=Ah0-2Ncg-eVMoRnu6OYJzQ31OQ@mail.gmail.com>
Josh Kupershmidt <schmiddy@gmail.com> writes:
> This bit of "Section 18.1. Setting Parameters"[1] is highly confusing:
Yeah, that's badly in need of editing.
> Second, I think Section 18.1 as a whole could be much improved by
> breaking it up into sub-sections; it seems too long and disjointed
> as-is. I gave this reorganization a shot with a larger patch
> (setting_parameters_subsections.diff) which includes the
> include_if_exists clarification, and also breaks the page up into
> three sub-sections.
I think this is a good idea, but I didn't like your section division
at all. I broke it up like this instead:
Parameter Names and Values
Setting Parameters via the Configuration File
Other Ways to Set Parameters
Examining Parameter Settings
See what you think.
> This is my preferred fix (for now -- I'll try to
> send in some further explanation/consolidation of GUC contexts
> relevant to that page later).
Yeah, the discussion on the pg_settings page maybe should be moved here.
On the other hand, this is very introductory material, so it might not
be the best place for anything too detailed.
regards, tom lane
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: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, schmiddy@gmail.com
Subject: Re: Confusing section of 'Setting Parameters'
In-Reply-To: <20001.1336705532@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox