Re: fix stats_fetch_consistency value in postgresql.conf.sample

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: michael(at)paquier(dot)xyz, andres(at)anarazel(dot)de, nathandbossart(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: fix stats_fetch_consistency value in postgresql.conf.sample
Date: 2022-07-20 05:12:26
Message-ID: 20220720051226.GH12702@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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(at)telsasoft(dot)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

Attachment Content-Type Size
0001-wip-add-DYNAMIC_DEFAULT-for-settings-which-are-vary-.patch text/x-diff 8.3 KB
0002-Add-fileval-bootval-consistency-check-of-GUC-paramet.patch text/x-diff 8.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-07-20 05:14:21 Re: Memory leak fix in psql
Previous Message Peter Smith 2022-07-20 05:08:36 Re: Handle infinite recursion in logical replication setup