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

From Kyotaro Horiguchi
Subject Re: fix stats_fetch_consistency value in postgresql.conf.sample
Date
Msg-id 20220525.131140.1773417448061343533.horikyota.ntt@gmail.com
Whole thread Raw
In response to fix stats_fetch_consistency value in postgresql.conf.sample  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: fix stats_fetch_consistency value in postgresql.conf.sample  (Andres Freund <andres@anarazel.de>)
List 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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: fix stats_fetch_consistency value in postgresql.conf.sample
Next
From: Andres Freund
Date:
Subject: Re: fix stats_fetch_consistency value in postgresql.conf.sample