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 1mSq2v-00052Q-7c for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Sep 2021 00:23:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mSq2t-0003X3-V7 for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Sep 2021 00:23:31 +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 1mSq2t-0003Wv-IM for pgsql-hackers@lists.postgresql.org; Wed, 22 Sep 2021 00:23:31 +0000 Received: from mail-il1-x12f.google.com ([2607:f8b0:4864:20::12f]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mSq2m-0004zt-RL for pgsql-hackers@postgresql.org; Wed, 22 Sep 2021 00:23:30 +0000 Received: by mail-il1-x12f.google.com with SMTP id q14so812019ils.5 for ; Tue, 21 Sep 2021 17:23:24 -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=Mp4/pgwOjFplt4kHAGOnbnKKGo/K6uDe7pe30uwwnY4=; b=hrAxOe7pbTn8bzdWPFwiDjCLqAyhZt3mt4s3TO2c4VCGe8a0bDvD7AThYLk7VEldgr lrog8L+YFerY2xjkYIhb0C7EVdGboIHbh6hI4RuVmCCocud/+xo0Z889jzBfFgUwyIrL lANIMKRyvtwTLAAJQ0IR4a6t9mxOkKMQJTiv7qrN/9rQb/yfx7MQ/QNriTWOkvHg0BtH Il+fN09yw3y/XQMdnFs8sZQJ9sWubRfQlbwlGvVcy3G0GVBXTTML3dNXei0auimCRE8b lvWNYwEHDjlr428sFdZpILE6qfz2m9C5gqVfaol/5PY7Vf/QcEOmAywUa5pUQjAaME7z Jn3w== 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=Mp4/pgwOjFplt4kHAGOnbnKKGo/K6uDe7pe30uwwnY4=; b=gzkh1xBtaN63OnisaCv8CDYbgl4BviYIHQ5NTVUimrAUnRNqR3YQ7afx7xzhT4SyOU ulBr60Ib58yuI1n7N7ZvYjKIXDN2MTTU024ZjD5AY8y6WBTSmcRZPrGkPLQXUaxKnn+/ onfzMhOVfZ4LpZx3uhw8Qh2jzSBYZTFQzYqFSxAH9yVND7sNCKfqMoZJcA4WXVGN6AnY re9MwZa/ch0Y1B3dUIY1s3tihmLIGHR6ehx8Jwqs/pJOsgnkvBsfDT9T8jn0Bkqfvcmv 8Vq7Pid8TO8xK2HwKFtZMteDucy8JsnWzP4/RTkoyzuELqY6mlkoSGIO/PSP+flgA17e ylow== X-Gm-Message-State: AOAM531auqy0o9uLEAUXroDW5+n4sZ7HNbdO1o9hTVmRcZI1KuOENq3S HWyvSFRw0S/Scn3NcrgOpffOxg== X-Google-Smtp-Source: ABdhPJyrOTKQDEmVbTE8MNA/zDJLUBXyQokymnZemxOSXsTreUWkv110BMgg4wRFde3zALPLwJiHdw== X-Received: by 2002:a05:6e02:1a21:: with SMTP id g1mr17454273ile.308.1632270203856; Tue, 21 Sep 2021 17:23:23 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id h1sm245128iow.12.2021.09.21.17.23.23 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Sep 2021 17:23:23 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 3BA9E800837; Tue, 21 Sep 2021 19:23:22 -0500 (CDT) Date: Tue, 21 Sep 2021 19:23:22 -0500 From: Justin Pryzby To: Fujii Masao Cc: "Shinoda, Noriyoshi (PN Japan FSIP)" , Kyotaro Horiguchi , pgsql-hackers@postgresql.org, rjuju123@gmail.com, tgl@sss.pgh.pa.us Subject: Re: Improve logging when using Huge Pages Message-ID: <20210922002322.GS831@telsasoft.com> References: <20210907131653.GK26465@telsasoft.com> <20210908.111736.355857044349579789.horikyota.ntt@gmail.com> <7ad09915-d8b1-1bce-b962-7062e2cf346a@oss.nttdata.com> <20210917.131430.1276120422145591578.horikyota.ntt@gmail.com> <80872660-ad16-3040-0a25-bd741faa5fc0@oss.nttdata.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <80872660-ad16-3040-0a25-bd741faa5fc0@oss.nttdata.com> 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 Wed, Sep 22, 2021 at 02:03:11AM +0900, Fujii Masao wrote: > Another idea is to output "Anonymous shared memory was allocated with > huge pages" when it's successfully allocated with huge pages, and to output > "Anonymous shared memory was allocated without huge pages" > when it's successfully allocated without huge pages. I'm not sure if users > may think even this message is noisy, though. +1 Maybe it could show the page size instead of "with"/without: "Shared memory allocated with 4k/1MB/1GB pages." -- Justin