Re: fix stats_fetch_consistency value in postgresql.conf.sample

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: fix stats_fetch_consistency value in postgresql.conf.sample
Date: 2022-05-25 04:08:08
Message-ID: Yo2rqJjurjLEFLaj@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 24, 2022 at 03:01:47PM -0700, Nathan Bossart wrote:
> 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.

Yes, postgresql.conf.sample should reflect the default, and that's
PGSTAT_FETCH_CONSISTENCY_CACHE in guc.c. Andres, shouldn't
pgstat_fetch_consistency be initialized to the same in pgstat.c?
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2022-05-25 04:11:40 Re: fix stats_fetch_consistency value in postgresql.conf.sample
Previous Message Amit Langote 2022-05-25 04:04:31 Re: First draft of the PG 15 release notes