Re: fix stats_fetch_consistency value in postgresql.conf.sample
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: michael@paquier.xyz, andres@anarazel.de, nathandbossart@gmail.com, pgsql-hackers@postgresql.org
Date: 2022-07-20T05:12:26Z
Lists: pgsql-hackers
Attachments
On Tue, Jul 19, 2022 at 03:04:27PM +0900, Kyotaro Horiguchi wrote: > At Wed, 13 Jul 2022 18:54:45 -0500, Justin Pryzby <pryzby@telsasoft.com> wrote in > > On Thu, Jul 14, 2022 at 08:46:02AM +0900, Michael Paquier wrote: > > > On Wed, Jul 13, 2022 at 12:30:00PM -0500, Justin Pryzby wrote: > > > > How did you make this list ? Was it by excluding things that failed for you ? > > Yes. I didn't confirm each variable. They are the variables differ on > RHEL-family OSes. io_concurrency differs according to > USE_PREFETCH. Regarding to effects of macro definitions, I searched > guc.c for non-GUC_NOT_IN_SAMPLE variables with macro-affected defaults. I think you'd also need to handle the ones which are changed by initdb.c. This patch takes Andres' suggestion. The list of GUCs I flagged is probably incomplete, maybe inaccurate, and at least up for discussion. BTW I still think it might have been better to leave pg_settings_get_flags() deliberately undocumented. -- Justin
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