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 1t3zgI-00Fnl2-JW for pgsql-hackers@arkaria.postgresql.org; Thu, 24 Oct 2024 15:23:22 +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 1t3zgG-004X7L-TH for pgsql-hackers@arkaria.postgresql.org; Thu, 24 Oct 2024 15:23:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t3zgG-004X7D-JB for pgsql-hackers@lists.postgresql.org; Thu, 24 Oct 2024 15:23:20 +0000 Received: from oss.nttdata.com ([49.212.34.109]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t3zgE-002kqC-Rj for pgsql-hackers@postgresql.org; Thu, 24 Oct 2024 15:23:20 +0000 Received: from [192.168.11.5] (p3718202-ipxg13301funabasi.chiba.ocn.ne.jp [114.166.227.202]) by oss.nttdata.com (Postfix) with ESMTPSA id D2EE16053A; Fri, 25 Oct 2024 00:23:15 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at oss.nttdata.com Message-ID: <948fd11c-cd13-4b29-98e3-0ca163537d42@oss.nttdata.com> Date: Fri, 25 Oct 2024 00:23:15 +0900 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Refactor GetLockStatusData() by skipping unused backends and groups To: Bertrand Drouvot Cc: pgsql-hackers@postgresql.org References: <5a0f78d1-0f56-439b-b4d3-2bae9d262c6c@oss.nttdata.com> Content-Language: en-US From: Fujii Masao In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2024/10/24 11:12, Bertrand Drouvot wrote: >> So, probably >> we can consider that this check is already in place. If it’s still worth adding, >> perhaps placing it inside the FAST_PATH_SLOT() macro could be an option... >> Or current assertion check is enough? Thought? > > Given that it's already done in FAST_PATH_GET_BITS(), I think that's fine as it > is and v2 LGTM. Thanks for the review! Pushed. Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION