Re: BUG #5656: parameter 'client_min_messages' accept values not listed in enumvals

From: Euler Taveira de Oliveira <euler(at)timbira(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: thommy <der(dot)thommy(at)gmx(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5656: parameter 'client_min_messages' accept values not listed in enumvals
Date: 2010-09-14 17:18:59
Message-ID: 4C8FAE83.4020900@timbira.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane escreveu:
> "thommy" <der(dot)thommy(at)gmx(dot)net> writes:
>> I just came across a small inconsistency:
>
>> pg=# select enumvals from pg_settings where name='client_min_messages';
>> enumvals
>> ---------------------------------------------------------------
>> {debug5,debug4,debug3,debug2,debug1,log,notice,warning,error}
>
> It's intentional that PANIC isn't listed there (nor is FATAL),
> on the grounds that it's not really a useful setting.
>
Fine. But shouldn't we remove these options from docs and/or code?

--
Euler Taveira de Oliveira
http://www.timbira.com/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Bahls 2010-09-14 17:44:16 Re: BUG #5657: wrong entry in sql_features
Previous Message Tom Lane 2010-09-14 16:37:36 Re: BUG #5656: parameter 'client_min_messages' accept values not listed in enumvals