Re: fix stats_fetch_consistency value in postgresql.conf.sample

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: michael(at)paquier(dot)xyz, andres(at)anarazel(dot)de, nathandbossart(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: fix stats_fetch_consistency value in postgresql.conf.sample
Date: 2022-07-28 22:27:34
Message-ID: 20220728222734.GA1913@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Note that this can currently exposes internal elog() errors to users:

postgres=# select pg_normalize_config_value('log_min_messages','abc');
WARNING: invalid value for parameter "log_min_messages": "abc"
HINT: Available values: debug5, debug4, debug3, debug2, debug1, info, notice, warning, error, log, fatal, panic.
ERROR: could not find enum option 0 for log_min_messages

postgres=# \errverbose
ERROR: XX000: could not find enum option 0 for log_min_messages
LOCATION: config_enum_lookup_by_value, guc.c:7284

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2022-07-28 22:29:41 Re: Cygwin cleanup
Previous Message Nathan Bossart 2022-07-28 22:26:02 Re: predefined role(s) for VACUUM and ANALYZE