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 1oLH5X-0001oy-Oa for pgsql-hackers@arkaria.postgresql.org; Tue, 09 Aug 2022 04:43:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oLH5V-0008HV-Pz for pgsql-hackers@arkaria.postgresql.org; Tue, 09 Aug 2022 04:43:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oLH5V-0008HM-Do for pgsql-hackers@lists.postgresql.org; Tue, 09 Aug 2022 04:43:29 +0000 Received: from mail-pj1-x1033.google.com ([2607:f8b0:4864:20::1033]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oLH5O-0005jx-HY for pgsql-hackers@postgresql.org; Tue, 09 Aug 2022 04:43:28 +0000 Received: by mail-pj1-x1033.google.com with SMTP id t22-20020a17090a449600b001f617f2bf3eso713994pjg.0 for ; Mon, 08 Aug 2022 21:43:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc; bh=EK6b94Mvi7TV+bohYDC5Cwi3xJV+in60MxbrLeqpnwQ=; b=HUT8IU3UwKxHu7BQwd3jU7tfTjtUsL1ofmUVyLuS/maR1vycPRYt5s+QlToRkMz9hZ QN4r2KFUzN4J9v1eZifow0K0+HYD8iQzVif88mVu/YLIqAXdM+Z/YNSnnDucGPXLbF3G 0eZam3uNtUENrAYw48E5ji7TE2hAAeR64q4fdailA5EU2ZIgy9n+8swvTMeKfuauO54c MuV1SN2wD7oc0+fdBjVXxXHLuwGazv9P8L+PWIAOxlw4LPPeM1eJWdQ2aEu8XnLkUHUv 1KHLufFiAJoTdt7OexlKPa1yeW/qeN3HxjyehGEHG0B+rshNrtoHt+h12TFx8w5nQJhp hkQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=EK6b94Mvi7TV+bohYDC5Cwi3xJV+in60MxbrLeqpnwQ=; b=I93yY04jH40Egh8t+hZDGTXdJHujcf6Q/hrLfjy2C1M8fizlbc74BbrIkGMR3qH/tS x4j53RJNS/CiAX6DA5UIGeZCkL8RiZEI3jbGEonm2mN650JU5iSoyXQJbySgxwJlBQK2 EtFwWjEoGZip2a6PlgiJMi5PgeIqqp+/Uduh441tESd4DyD1rqZXjyyrJF2K4279nWgX 5qtXQxwjqYrKNfK+P5exZJe0WR0qd2YUBvAHyYu5Hh7QmQJwComQ0C85YaoToCIeiFBl iPS4R0KVBVoFhQ/5DIX5+DrHufAxQESYufgdRSkCwD30+Crs7DztU7vwejS4f+ointv6 VmUg== X-Gm-Message-State: ACgBeo0Mu2jnAm9wx7OrnaSkgnruhDK22qvm4ge7DWVdIN8EerAc27OZ 73fhNLF50e9/jtAr5GXUlS8= X-Google-Smtp-Source: AA6agR6NmYho+o/hbKtPjWYJGIWYnhTim1W0fTZUHOCJ8tutP8PJ+wh8ET1X3DgCNNK6HSECMu6AyA== X-Received: by 2002:a17:903:18a:b0:16f:9027:60dc with SMTP id z10-20020a170903018a00b0016f902760dcmr18117268plg.147.1660020200241; Mon, 08 Aug 2022 21:43:20 -0700 (PDT) Received: from nathanxps13 ([50.54.155.70]) by smtp.gmail.com with ESMTPSA id d12-20020a630e0c000000b00419b128cf98sm7170531pgl.54.2022.08.08.21.43.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 08 Aug 2022 21:43:19 -0700 (PDT) Date: Mon, 8 Aug 2022 21:43:17 -0700 From: Nathan Bossart To: Bharath Rupireddy Cc: John Naylor , Andres Freund , John Naylor , pgsql-hackers Subject: Re: optimize lookups in snapshot [sub]xip arrays Message-ID: <20220809044317.GA1443152@nathanxps13> References: <20220804221551.GA1090071@nathanxps13> <20220805202510.GA1208450@nathanxps13> <20220805220434.6h2aa7eww5rxird6@awork3.anarazel.de> <20220806181326.GA1216305@nathanxps13> <20220806212522.GA1221353@nathanxps13> <20220808230716.GB1393216@nathanxps13> 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 Tue, Aug 09, 2022 at 09:40:15AM +0530, Bharath Rupireddy wrote: > Isn't it a good idea to capture the above two points as comments in > port/pg_lfind.h just to not lose track of it? I know these are present > in the hackers thread, but having them in the form of comments helps > developers who attempt to change or use the new function. Hm. My first impression is that this is exactly the sort of information that is better captured on the lists. I'm not sure that the lack of such commentary really poses any threat for future changes, which would need to be judged on their own merit, anyway. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com