Re: fix stats_fetch_consistency value in postgresql.conf.sample
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: pryzby@telsasoft.com, michael@paquier.xyz, nathandbossart@gmail.com, pgsql-hackers@postgresql.org
Date: 2022-05-28T20:22:45Z
Lists: pgsql-hackers
Hi,
On 2022-05-26 16:27:53 +0900, Kyotaro Horiguchi wrote:
> It could be in SQL, but *I* prefer to use perl for this, since it
> allows me to write a bit complex things (than simple string
> comparison) simpler.
I wonder if we shouldn't just expose a C function to do this, rather than
having a separate implementation in a tap test.
> +# parameter names that cannot get consistency check performed
> +my @ignored_parameters =
I think most of these we could ignore by relying on source <> 'override'
instead of listing them?
> +# parameter names that requires case-insensitive check
> +my @case_insensitive_params =
> + ('ssl_ciphers',
> + 'log_filename',
> + 'event_source',
> + 'log_timezone',
> + 'timezone',
> + 'lc_monetary',
> + 'lc_numeric',
> + 'lc_time');
Why do these differ by case?
Greetings,
Andres Freund
Commits
-
Align stats_fetch_consistency definition with guc.c default.
- 0107855b1480 15.0 landed
-
Fix stats_fetch_consistency default value indicated in postgresql.conf.sample.
- 98f897339b01 15.0 landed