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 1lQDNQ-0007PL-F1 for pgsql-hackers@arkaria.postgresql.org; Sat, 27 Mar 2021 18:09:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lQDNO-0007oo-1z for pgsql-hackers@arkaria.postgresql.org; Sat, 27 Mar 2021 18:09:34 +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 1lQDNN-0007og-24 for pgsql-hackers@lists.postgresql.org; Sat, 27 Mar 2021 18:09:33 +0000 Received: from [64.147.123.19] (helo=wout3-smtp.messagingengine.com) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lQDNJ-00013F-IG for pgsql-hackers@lists.postgresql.org; Sat, 27 Mar 2021 18:09:32 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 3D6DA159B; Sat, 27 Mar 2021 14:09:17 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Sat, 27 Mar 2021 14:09:17 -0400 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:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=+yaLfqWFI2iSZpfg2K8sbDEk0occKCUyNtlrD9k7CqQ=; b=ljVTAuy5 Ws/AocCK7N1W4qJMplxz4EWGMAvJzmQ48nMX9S4j4JytG1aw+hR0in4E92GfyJGp m34/JTnBNSa/vWdnUP/hsTNYImnO5s7Qpea+XE5BZ3qblEh+ro/PODCrZWRmCpih BOPcNtLvwyRfMeIMq14jHFq0Sqr+g0uOKRHeYr0xM6qk+lxMlknNuT9WEsS0OLfG aiz6t1vbjWhGnxqFOZuGxKnTCbkkXWM5BisXrHHH/HWJZ5UPfQCVnd01uKas2CRa eo+gKp74lvD+dhYapHBah1tAlT25/gidAoEsVCRxCdh8n5RTN17fO48H3N1XkhtU t8z/DsKS7GAasA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudehgedguddutdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvuffkgggtugfgjggfsehtkeertddtredunecuhfhrohhmpeetlhhv rghrohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorh hgqeenucggtffrrghtthgvrhhnpeeufffhjeeiueeuffegvddukeegledtveeivdeiueef ieeivefgteehueefteehvdenucfkphepudeltddrleehrdduledrleehnecuvehluhhsth gvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhhvghrrhgvsegr lhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.19.95]) by mail.messagingengine.com (Postfix) with ESMTPA id D741124005D; Sat, 27 Mar 2021 14:09:15 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 2DF072A091B; Sat, 27 Mar 2021 15:09:13 -0300 (-03) Date: Sat, 27 Mar 2021 15:09:13 -0300 From: Alvaro Herrera To: Tomas Vondra Cc: John Naylor , PostgreSQL Hackers Subject: Re: WIP: BRIN multi-range indexes Message-ID: <20210327180913.GA3088@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1da94012-f512-ffc8-dd5e-888d862b662e@enterprisedb.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Host-Lookup-Failed: Reverse DNS lookup failed for 64.147.123.19 (deferred) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-Mar-26, Tomas Vondra wrote: > Hi, > > I've pushed both the bloom and minmax-multi indexes today. One thing I've been wondering all along is how useful are these BRIN-backed bloom indexes compared to contrib-supplied bloom indexes. My guess is that the BRIN implementation has some advantage, or you would not have worked so much on it. But what is it? Thanks -- Álvaro Herrera Valdivia, Chile