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-09-13 00:43:03
Message-ID: 20220913004303.GM31833@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Checking if you're planning to work on this patch still ?

On Thu, Jul 28, 2022 at 05:27:34PM -0500, Justin Pryzby wrote:
> 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 Andres Freund 2022-09-13 01:06:23 Re: [RFC] building postgres with meson - v12
Previous Message Ranier Vilela 2022-09-12 23:56:46 Re: Fix possible bogus array out of bonds (src/backend/access/brin/brin_minmax_multi.c)