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 1lRuKC-0002VG-2x for pgsql-hackers@arkaria.postgresql.org; Thu, 01 Apr 2021 10:13:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lRuKB-0007OR-0K for pgsql-hackers@arkaria.postgresql.org; Thu, 01 Apr 2021 10:13:15 +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 1lRuKA-0007K9-Pg for pgsql-hackers@lists.postgresql.org; Thu, 01 Apr 2021 10:13:14 +0000 Received: from oss.nttdata.com ([49.212.34.109]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lRuK4-0000ZM-GE for pgsql-hackers@postgresql.org; Thu, 01 Apr 2021 10:13:13 +0000 Received: from hnk.local (p2350207-ipbf2126funabasi.chiba.ocn.ne.jp [114.167.184.207]) by oss.nttdata.com (Postfix) with ESMTPSA id 8801062829; Thu, 1 Apr 2021 19:13:05 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.102.3 at oss.nttdata.com Subject: Re: Get memory contexts of an arbitrary backend process To: Kyotaro Horiguchi , torikoshia@oss.nttdata.com Cc: pgsql-hackers@postgresql.org, tgl@sss.pgh.pa.us, gkokolatos@protonmail.com, kasahara.tatsuhito@gmail.com, craig@2ndquadrant.com References: <1f259e90-08c8-2202-be66-f7ee05d22cd2@oss.nttdata.com> <20210331.151612.259240960686480846.horikyota.ntt@gmail.com> From: Fujii Masao Message-ID: <65fbf059-bcff-1585-59a1-1ec6a6f5ac75@oss.nttdata.com> Date: Thu, 1 Apr 2021 19:13:05 +0900 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.9.0 MIME-Version: 1.0 In-Reply-To: <20210331.151612.259240960686480846.horikyota.ntt@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021/03/31 15:16, Kyotaro Horiguchi wrote: >> + The memory contexts will be logged based on the log configuration >> set. For example: >> >> How do you think? > > How about "The memory contexts will be logged in the server log" ? > I think "server log" doesn't suggest any concrete target. Or just using "logged" is enough? Also I'd like to document that one message for each memory context is logged. So what about the following? One message for each memory context will be logged. For example, > +1 from me. It looks like more compliant with the standard? +1, too. Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION