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 1l1m1j-0000jC-Jn for pgsql-hackers@arkaria.postgresql.org; Tue, 19 Jan 2021 08:06:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l1m1i-0002fL-6j for pgsql-hackers@arkaria.postgresql.org; Tue, 19 Jan 2021 08:06:10 +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 1l1m1h-0002fD-VY for pgsql-hackers@lists.postgresql.org; Tue, 19 Jan 2021 08:06:09 +0000 Received: from forward1-smtp.messagingengine.com ([66.111.4.223]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l1m1c-0003D9-Sd for pgsql-hackers@postgresql.org; Tue, 19 Jan 2021 08:06:08 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailforward.nyi.internal (Postfix) with ESMTP id 57083195A477; Tue, 19 Jan 2021 03:06:03 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 19 Jan 2021 03:06:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=Q1QQqo2mLf3SacUcoZjo5rWCEyDNi62R1Z1jNK/zJ 68=; b=gdP2jKVv+uc6djUPrDmn4po3Sg7DSaGNAV71om91g0okafXwIENvhHowp 4wTdhD1jgfeBmlwMQdEAdMEW92VWqNXHydPfz5pdaTPsowt45BhfNO6kErFwuSR/ SgKVBk6pZP7/ihpK79ueH9+926g6YELv8GiWpgfAsxUNAv8iK9OJ+4WBSkVdNJMF /4bd+OKyQQ1OX50/YZsAMNaxHqCqFhYxcqzQZ4w6WpWnIMmiAqx7v3J+V+HkPQS6 Ca7cOItLv2NNqBdACIhtxVPbbkTIeA17tU7E8J3Nt8EG+oixELRZKwEHesadlsoY smQ4V80dDH+gzok5KFLhgwJkzd5sg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrtdelgdduudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhohfkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeetgfegieevieegheel jeegledukedvffeltefgkefgfeevjeeujeeuhfefteduheenucffohhmrghinhepfihikh hiphgvughirgdrohhrghenucfkphepkeejrddujeejrdejvddrudegvdenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvg hnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: from april.pezone.net (p57b1488e.dip0.t-ipconnect.de [87.177.72.142]) by mail.messagingengine.com (Postfix) with ESMTPA id 65ED61080064; Tue, 19 Jan 2021 03:06:01 -0500 (EST) Subject: Re: popcount To: Tom Lane References: <20201230105535.GJ13234@fetter.org> <5ea2932e-50f5-4a74-9550-5e3291b6652b@manitou-mail.org> <20201230164108.GK13234@fetter.org> <20210111161354.GA8721@fetter.org> <338981.1610984050@sss.pgh.pa.us> Cc: David Fetter , Daniel Verite , PostgreSQL Development , Vik Fearing From: Peter Eisentraut Organization: EnterpriseDB Message-ID: Date: Tue, 19 Jan 2021 09:06:00 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <338981.1610984050@sss.pgh.pa.us> 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: Precedence: bulk On 2021-01-18 16:34, Tom Lane wrote: > Peter Eisentraut writes: >> [ assorted nits ] > > At the level of bikeshedding ... I quite dislike using the name "popcount" > for these functions. I'm aware that some C compilers provide primitives > of that name, but I wouldn't expect a SQL programmer to know that; > without that context the name seems pretty random and unintuitive. > Moreover, it invites confusion with SQL's use of "pop" to abbreviate > "population" in the statistical aggregates, such as var_pop(). I was thinking about that too, but according to , popcount is an accepted high-level term, with "pop" also standing for "population".