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 1nC8mF-0005KK-BC for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Jan 2022 23:29:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nC8mD-0007ID-7L for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Jan 2022 23:29:33 +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 1nC8mC-0007I3-Um for pgsql-hackers@lists.postgresql.org; Mon, 24 Jan 2022 23:29:32 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nC8m6-0002nU-Gp for pgsql-hackers@postgresql.org; Mon, 24 Jan 2022 23:29:31 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 20ONTOfQ2164898; Mon, 24 Jan 2022 18:29:24 -0500 From: Tom Lane To: Andreas Karlsson cc: Peter Eisentraut , pgsql-hackers Subject: Re: btree_gist into core? In-reply-to: References: <5fd19680-c0db-e9ea-eae6-971a369b4233@enterprisedb.com> Comments: In-reply-to Andreas Karlsson message dated "Tue, 25 Jan 2022 00:10:30 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2164896.1643066964.1@sss.pgh.pa.us> Date: Mon, 24 Jan 2022 18:29:24 -0500 Message-ID: <2164897.1643066964@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andreas Karlsson writes: > On 1/19/22 09:30, Peter Eisentraut wrote: >> I don't have a lot of experience with this module, so I don't know if >> there are any lingering concerns about whether it is mature enough as a >> built-in feature. > While it I like the idea on a conceptual level I worry about the code > quality of the module. I know that the btree/cidr code is pretty broken. > But I am not sure if there are any issues with other data types. Yeah :-(. We just fixed an issue with its char(n) support too (54b1cb7eb), so I don't have a terribly warm feeling about the quality of the lesser-used code paths. Still, maybe we could do some code review/testing rather than a blind copy & paste. I'd also opine that we don't have to preserve on-disk compatibility while migrating into core, which'd help get out of the sticky problem for inet/cidr. This'd require being able to run the contrib module alongside the core version for awhile (to support existing indexes), but I think we could manage that if we tried. IIRC we did something similar when we migrated tsearch into core. One thing I don't know anything about is how good are btree_gist indexes performance-wise. Do they have problems that we'd really need to fix to consider them core-quality? regards, tom lane