Skip site navigation (1) Skip section navigation (2)

Re: explaining "context" column of pg_settings

From: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
To: Euler Taveira de Oliveira <euler(at)timbira(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: explaining "context" column of pg_settings
Date: 2010-12-18 03:46:57
Message-ID: AANLkTi=Da7C635U5tzmkkPh7rOynpN+-oYjsVyXdup5P@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-docs
On Fri, Dec 17, 2010 at 1:08 PM, Euler Taveira de Oliveira
<euler(at)timbira(dot)com> wrote:
> Alvaro Herrera escreveu:
>> Perhaps we can replace the current "this setting requires a restart"
>> boilerplate with "this setting has context foo" in setting descriptions,
>> and have a pointer to wherever the description of each context is.
>>
> .. or even foo_param (integer) (restart)
>
> 'restart' is a link describing the context. When I'm reading the manual
> searching for a parameter description, sometimes it is not clear what is the
> context; in this case, I need to query pg_settings to figure out what I have
> to do to change that parameter. It would be fine if that information was
> easily available.

I definitely like the idea of explicitly stating the context of all
the GUCs in some concise yet clear way. I'm not totally sold on:

foo_param (integer) (restart)

since the (restart) is too similar to the (integer). I'm not sure I
have a better proposal offhand though. Maybe something like:

foo_param (integer) [postmaster context]

with "postmaster" a link to wherever we put the context descriptions.
I bet someone can find a prettier way, I'm still not happy with the
above..

Josh

In response to

pgsql-docs by date

Next:From: Tom LaneDate: 2010-12-18 03:59:40
Subject: Re: explaining "context" column of pg_settings
Previous:From: Robert HaasDate: 2010-12-18 03:45:32
Subject: Re: explaining "context" column of pg_settings

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group