Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t0snl-00Ddgg-0K for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Oct 2024 01:26:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t0snj-00Dyf9-7y for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Oct 2024 01:26:11 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t0sni-00Dyf0-U0 for pgsql-hackers@lists.postgresql.org; Wed, 16 Oct 2024 01:26:11 +0000 Received: from mail-io1-xd32.google.com ([2607:f8b0:4864:20::d32]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t0sng-0015v9-Nn for pgsql-hackers@postgresql.org; Wed, 16 Oct 2024 01:26:10 +0000 Received: by mail-io1-xd32.google.com with SMTP id ca18e2360f4ac-836f1b47cdfso290763839f.0 for ; Tue, 15 Oct 2024 18:26:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729041968; x=1729646768; darn=postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=7dzO7gB+pwvXYJUtWJBY4AIhzsThtR7BiAdWzGUW/YY=; b=KkCToYARTh9yp0fWVhHidhunjv5jMR3NMR546WUl6Vr7OtY5W+6Cberrzl6T/YSbWI tAmalH5oNwwu1iZ2Jui+qWlh/ggyTVAVhw4SM2+coMEB1xSF/joSIMhulyKKJwhVmzpY PTmouXr7yHE8NArtmdQYruSApYhKtE83BAqqPaNjAwZaE+hpK6ZVwKNupJ+1Yv1SQYCE RaSoR6RpISPuG184uSpCx8iKKWTEmYTqH2eSKqlV4tJBOoyUYqvbKptIf7o7FUmXTxI2 UU9el5nXAJmDlBhiUUyrp8lEXBM7DMLd9Cp/RFbgXRRqvcEv5dnPwZMg+t2rr1YblxE7 mbTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729041968; x=1729646768; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=7dzO7gB+pwvXYJUtWJBY4AIhzsThtR7BiAdWzGUW/YY=; b=FDmzunbbYw3poJ4Sm9R3niHeRNY/taGLEnLIYHjEVxc9X4LXl5vXAMBKec/m2jTBym RZSYTfElcMjj62M4k9+b/w83IFzhtMjrdfVrY53cOBpn/+1DFfiK87UfcxZsbou6AEe3 0X6uiP8onaYMEhMLjAlY4hCVux/bIGJJ/g7XS3RYZqNzbh1Q0ZBAtj0viyXNkp/5PpU+ +V7Awxa5SNcGjYNOwepo5kshxcz2Uz1gjleoQR53ovTKkOL7T4xQl2ZEnyquGx9BGVLZ Y+cigUVM0N+WRUmORhavLV6m8FNVlsacKBwD9SFMR2UqKi7VvGaY5mledrRMNOH6ycor wscA== X-Forwarded-Encrypted: i=1; AJvYcCVH1Q8TZyWeHgKB7iT+7Q4BuGArwhMiqXihkKB1PowHrnhc7N6viXur7N+g2O+kGxlOXGXrknq0+t+IjhBq@postgresql.org X-Gm-Message-State: AOJu0YxLTqHAMubIq7i2G96jpQzaoPDa5OJwakFqJy9llAgSlz5GiqSn 5aawLIfx2api2kXExD+TYmgmAJGxfMshzxPMOsPt+qvLMxgaAU3Q X-Google-Smtp-Source: AGHT+IHEj50XceUvL9UP33U668q5tUnaDHiSPxaB7Ehk9Yo17tf+udkSa75BAGiZ3FmkweXMZL38FQ== X-Received: by 2002:a05:6e02:12c9:b0:3a3:972a:3991 with SMTP id e9e14a558f8ab-3a3b602268dmr159473105ab.16.1729041967748; Tue, 15 Oct 2024 18:26:07 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id 8926c6da1cb9f-4dbec9b1732sm575578173.50.2024.10.15.18.26.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 15 Oct 2024 18:26:07 -0700 (PDT) Date: Tue, 15 Oct 2024 20:26:06 -0500 From: Nathan Bossart To: Michael Paquier Cc: Seino Yuki , pgsql-hackers@postgresql.org Subject: Re: Doc: shared_memory_size_in_huge_pages with the "SHOW" command. Message-ID: References: <420584fd274f9ec4f337da55ffb3b790@oss.nttdata.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Oct 16, 2024 at 09:31:49AM +0900, Michael Paquier wrote: > I am not sure that neither mentioning nor recommending SHOW for this > area is a good idea, the point being to encourage its use before the > server is running as we don't want to allocate anything when tuning > it. Agreed. > Point taken that the current wording can be confusing because of the > "*must* be shut down". How about doing a simpler s/must/should/ for a > softer wording? Well, the point is that you can't use "postgres -C" to view this GUC while the server is running. I can see how the present wording might be misinterpreted, though. Perhaps we should change this sentence to something like: Note that the server must be shut down to view this runtime-computed parameter with the postgres command. -- nathan