Re: fix stats_fetch_consistency value in postgresql.conf.sample - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: fix stats_fetch_consistency value in postgresql.conf.sample
Date
Msg-id 20220913004303.GM31833@telsasoft.com
Whole thread Raw
In response to Re: fix stats_fetch_consistency value in postgresql.conf.sample  (Michael Paquier <michael@paquier.xyz>)
Responses Re: fix stats_fetch_consistency value in postgresql.conf.sample
List 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



pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: Fix possible bogus array out of bonds (src/backend/access/brin/brin_minmax_multi.c)
Next
From: Andres Freund
Date:
Subject: Re: [RFC] building postgres with meson - v12