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 1mNayB-0001Oe-KR for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Sep 2021 13:16:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mNayA-0003Pd-KA for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Sep 2021 13:16:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mNayA-0003PV-9k for pgsql-hackers@lists.postgresql.org; Tue, 07 Sep 2021 13:16:58 +0000 Received: from mail-io1-xd32.google.com ([2607:f8b0:4864:20::d32]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mNay7-0004YU-TM for pgsql-hackers@postgresql.org; Tue, 07 Sep 2021 13:16:57 +0000 Received: by mail-io1-xd32.google.com with SMTP id n24so12703155ion.10 for ; Tue, 07 Sep 2021 06:16:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=dH3PmNWed3V15rphT+mlnN/kRSd8J0Uq3hw1OxZi+2A=; b=luLyu16EBrcA6HFLGQ452eSqLyxV5jl5KQ4qzo3iV9lDOcMgC4aablKi4IM6xpO3K+ 8QB1xAhuHw8inJywadAVwq1UnzdBNrAirEriw0IKgAgIccObFXskgFejkjkNso36HtnO QkHoVb6j6FecJ59PwmFNIc2v/MbcEcBdjiEC/d2VbqGJjbgLgz2Wl9es8Uquilr7eB14 CqQR3woqNpo/5lrRs6eLI7p1pAF5avLm5qn81W3PSa0QJ8xHCHhV7Yx4k39OtwbYB1m4 BtoB6t8Arf/eIyLLf/3Mvgg5/MGaWWAUNqj0Jz9b4WnMsgpnb/ibvltwNGzpIKKQ8n0B ajKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=dH3PmNWed3V15rphT+mlnN/kRSd8J0Uq3hw1OxZi+2A=; b=d4YSyZXoOfhl+GLKbet1n8ISDdvpMHccAebPAS1XUo9mc1doLJY/JrBlnjPH8Ym0qq z6ij/GDZqHAJsJxuR3coVqqfkadfOjkyN+TeAvIFTV///OSW461wMwhB1VC8YcVsrNXm LvLn60c1ynEyt0+NZFqzoRH/7UEf1eG1fagW7OtA+AJmSL6PshDOfgcR2QSnRscwKDej q2X3pJWl5IE9I8vo/4b0ubLAFsanhMzGLROj1orJDiuBb9SeV3/boNsjVdRmGwXwHn/M p+MfpMgzrmBaDxSRuL1p2BfUmk3fsear/utSscKjGD9S+K/yavB4va2/fMe1kY8/TrgF t2yA== X-Gm-Message-State: AOAM530i7BhRsG2oai/6YgKvUrBzjrGUy16xZEh3Q5WhIVkrzcAam7RE E095tLFjJIYZHqbIVIg85oXSVA== X-Google-Smtp-Source: ABdhPJxMGAQ0rdVjVWON4MplFHR8kGLS2+Da9vrnKWh2ToDLLzM28CWKW9PHD2P2pHa22BKJHHywKQ== X-Received: by 2002:a6b:e90c:: with SMTP id u12mr13408221iof.95.1631020614754; Tue, 07 Sep 2021 06:16:54 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id t14sm6183937ilu.67.2021.09.07.06.16.54 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Sep 2021 06:16:54 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 3CEE0800359; Tue, 7 Sep 2021 08:16:53 -0500 (CDT) Date: Tue, 7 Sep 2021 08:16:53 -0500 From: Justin Pryzby To: Fujii Masao Cc: "Shinoda, Noriyoshi (PN Japan FSIP)" , pgsql-hackers@postgresql.org, Kyotaro Horiguchi , "rjuju123@gmail.com" , Tom Lane Subject: Re: Improve logging when using Huge Pages Message-ID: <20210907131653.GK26465@telsasoft.com> References: <7e5b9f6d-1db9-d1e2-3bd8-ef65f24b35be@oss.nttdata.com> <20210903.164934.1726669051525427478.horikyota.ntt@gmail.com> <1946f6b9-75a1-7aeb-7b06-6c018377e518@oss.nttdata.com> <2498302.1630679233@sss.pgh.pa.us> 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 Tue, Sep 07, 2021 at 07:12:36PM +0900, Fujii Masao wrote: > One big concern about the patch is that log message is always reported > when shared memory fails to be allocated with huge pages enabled > when huge_pages=try. Since huge_pages=try is the default setting, > many users would see this new log message whenever they start > the server. Those who don't need huge pages but just use the default > setting might think that such log messages would be noisy. I don't see this as any issue. We're only talking about a single message on each restart, which would be added in a major release. If it's a problem, the message could be a NOTICE or INFO, and it won't be shown by default. I think it should say "with/out huge pages" without "enabled/disabled", without "again", and without "The server", like: + (errmsg("could not map anonymous shared memory (%zu bytes)" + " with huge pages.", allocsize), + errdetail("Anonymous shared memory will be mapped " + "without huge pages."))); -- Justin