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

From Nathan Bossart
Subject fix stats_fetch_consistency value in postgresql.conf.sample
Date
Msg-id 20220524220147.GA1298892@nathanxps13
Whole thread Raw
Responses Re: fix stats_fetch_consistency value in postgresql.conf.sample
Re: fix stats_fetch_consistency value in postgresql.conf.sample
List pgsql-hackers
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.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

Attachment

pgsql-hackers by date:

Previous
From: Zhihong Yu
Date:
Subject: Re: enable/disable broken for statement triggers on partitioned tables
Next
From: Zhihong Yu
Date:
Subject: Re: adding status for COPY progress report