Re: fix stats_fetch_consistency value in postgresql.conf.sample

Kyotaro Horiguchi <horikyota.ntt@gmail.com>

From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: nathandbossart@gmail.com
Cc: pgsql-hackers@postgresql.org
Date: 2022-05-25T04:11:40Z
Lists: pgsql-hackers
At Tue, 24 May 2022 15:01:47 -0700, Nathan Bossart <nathandbossart@gmail.com> wrote in 
> In postgresql.conf.sample, stats_fetch_consistency is set to "none," but
> the default appears to be "cache."  Should these be consistent?  I've
> attached a patch to change the entry in the sample.

Good catch:)

The base C variable is inirtialized with none.
The same GUC is intialized with "cache".
The default valur for the GUC is "none" in the sample file.

I think we set the same value to C variable.  However, I wonder if it
would be possible to reduce the burden of unifying the three inital
values.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



Commits

  1. Align stats_fetch_consistency definition with guc.c default.

  2. Fix stats_fetch_consistency default value indicated in postgresql.conf.sample.