Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oBmC1-0001ca-Hu for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Jul 2022 23:54:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oBmC0-0007Te-71 for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Jul 2022 23:54:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oBmBz-0007Sj-Qo for pgsql-hackers@lists.postgresql.org; Wed, 13 Jul 2022 23:54:55 +0000 Received: from mail-io1-xd30.google.com ([2607:f8b0:4864:20::d30]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oBmBs-0004Oi-0O for pgsql-hackers@postgresql.org; Wed, 13 Jul 2022 23:54:55 +0000 Received: by mail-io1-xd30.google.com with SMTP id q14so90108iod.3 for ; Wed, 13 Jul 2022 16:54:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=sWPJUJ+y3PAS+9XZjVc6eGrenh+SrcDE5OOcKf2qTsg=; b=0K4tnK3gS5ly+nXCw54o4KLCfJt6WxO2WOONYVGcQHYmaN8aSn7JGUBJsnnR4F9XFA AInelUWNpP8cQLI50T9Q6q9fp7qWdmEZo3UNLRGYoJGJym8H2+/u3YdACYjvO/Irpu3e eCjauiJGZkGl2zCFOLGAnQ8vFbKzEg++Z/HANdZd+wR1kBDjQSbKtFTb35Ki0D9Img4u J/Z3lSW0q6bqA1U0URyBNIjLpug4SlOwrpPe13VjbFsshFAuuiQ+9ZzxE/4bc1YOQlnn XA81u5U2S+F54c/ZqWXtNDaw3hvUpNOh2I+2yn0PbSXcWda6zsyoHKpCNptK+yz44EAB qgGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=sWPJUJ+y3PAS+9XZjVc6eGrenh+SrcDE5OOcKf2qTsg=; b=pw5tuvom7bQ0dUrC1S9Q/YqKgqeln1loidbd87AdYT/xb6F92oZoNHQGH6y23ubYi4 NuxcIHyIJRXCJ47V9Eqw/ZJvZmPhdi2MnMGwu6EpI2ciXan/m+5pxobaNRge4bv4GN1P 6R6mHbCUragY7Oowy/kIzlw958hyFNucoGqaaKKwNWsmnPDKdavgPtjBGws0H5Z1yEQF KQhMkQsfjUGF70HmNNL2fkllO/VSrL+vYe4IiGpdQ54or1ojQv+ZtATUC+S1wz6eolqR MEcDSsmyNBpfEoFDFI2RipAWVbsdAmKZGx+uhbAjkCu0J+k3nwpMtc8pQVADniurSPq8 07GA== X-Gm-Message-State: AJIora+iuyyrsGWaGUv/pZl93jreUdND1gcEinwQTbg7PNe8AexzxYmC HC85IMTkV/gy8ZjnhxBL7TYapQ== X-Google-Smtp-Source: AGRyM1vOBbd3+Pk06hktYf4GFTDn2krcGE1oEK4x5wxbTwZAv5wxqYfvyMjPV7TBFBBvp9pXo6XOQg== X-Received: by 2002:a05:6638:1602:b0:341:3e1f:d862 with SMTP id x2-20020a056638160200b003413e1fd862mr27773jas.24.1657756486467; Wed, 13 Jul 2022 16:54:46 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id d13-20020a5d964d000000b006788259b526sm123037ios.41.2022.07.13.16.54.45 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Jul 2022 16:54:46 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 2FA77800934; Wed, 13 Jul 2022 18:54:45 -0500 (CDT) Date: Wed, 13 Jul 2022 18:54:45 -0500 From: Justin Pryzby To: Michael Paquier Cc: Kyotaro Horiguchi , andres@anarazel.de, nathandbossart@gmail.com, pgsql-hackers@postgresql.org Subject: Re: fix stats_fetch_consistency value in postgresql.conf.sample Message-ID: <20220713235444.GF18011@telsasoft.com> References: <20220616132306.GD29853@telsasoft.com> <20220617.094358.2201653243066915172.horikyota.ntt@gmail.com> <20220622230710.r2m4ex5tlf6mveyh@alap3.anarazel.de> <20220630.173801.662386227537019720.horikyota.ntt@gmail.com> <20220713173000.GD18011@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 ? > > > > cfbot is currently failing due to io_concurrency on windows. > > I think there are more GUC which should be included here. > > > > http://cfbot.cputube.org/kyotaro-horiguchi.html > > FWIW, I am not really a fan of making this test depend on a hardcoded > list of GUCs. The design strength of the existing test is that we > don't have such a dependency now, making less to think about in terms > of maintenance in the long-term, even if this is now run > automatically. It doesn't really need to be stated that an inclusive list wouldn't be useful. That's a list of GUCs to be excluded. Which is hardly different from the pre-existing list of exceptions. # Ignore some exceptions. next if $param_name eq "include"; next if $param_name eq "include_dir"; next if $param_name eq "include_if_exists"; -- Exceptions are transaction_*. SELECT name FROM tab_settings_flags WHERE NOT no_show_all AND no_reset_all ORDER BY 1; name ------------------------ transaction_deferrable transaction_isolation transaction_read_only (3 rows) How else do you propose to make this work for guc whose defaults vary by platform in guc.c or in initdb ? -- Justin