From: | "thommy" <der(dot)thommy(at)gmx(dot)net> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #5656: parameter 'client_min_messages' accept values not listed in enumvals |
Date: | 2010-09-14 13:13:42 |
Message-ID: | 201009141313.o8EDDgXh093771@wwwmaster.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 5656
Logged by: thommy
Email address: der(dot)thommy(at)gmx(dot)net
PostgreSQL version: 9.0rc1
Operating system: Windows
Description: parameter 'client_min_messages' accept values not listed
in enumvals
Details:
Hi there,
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}
Hmm, according to the documentation 'panic' is a valid value...
pg=# select set_config('client_min_messages', 'PANIC', false);
set_config
------------
panic
pg=# select name, setting, enumvals from pg_settings where
name='client_min_messages';
-[ RECORD 1 ]-----------------------------------------------------------
name | client_min_messages
setting | panic
enumvals | {debug5,debug4,debug3,debug2,debug1,log,notice,warning,error}
Maybe this can be fixed before the final release of 9.0
Regards, thommy
From | Date | Subject | |
---|---|---|---|
Next Message | thommy | 2010-09-14 14:08:07 | BUG #5657: wrong entry in sql_features |
Previous Message | Peter Eisentraut | 2010-09-14 11:10:04 | Re: 9.0 Bug: cannot build against python3.1, with two versions of python in the environment |