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 1uhgWU-002kdn-A8 for pgsql-bugs@arkaria.postgresql.org; Fri, 01 Aug 2025 03:33:34 +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 1uhgWT-004zsM-5y for pgsql-bugs@arkaria.postgresql.org; Fri, 01 Aug 2025 03:33:33 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uhgWS-004zsD-TP for pgsql-bugs@lists.postgresql.org; Fri, 01 Aug 2025 03:33:32 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uhgWQ-0007c6-15 for pgsql-bugs@lists.postgresql.org; Fri, 01 Aug 2025 03:33:32 +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 5713XSAb2189028; Thu, 31 Jul 2025 23:33:28 -0400 From: Tom Lane To: Richard Guo cc: Peter Eisentraut , exclusion@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops In-reply-to: References: <19000-2525470d200672ab@postgresql.org> <2107725.1753985855@sss.pgh.pa.us> Comments: In-reply-to Richard Guo message dated "Fri, 01 Aug 2025 11:38:31 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2189026.1754019208.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Thu, 31 Jul 2025 23:33:28 -0400 Message-ID: <2189027.1754019208@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Richard Guo writes: > On Fri, Aug 1, 2025 at 3:17 AM Tom Lane wrote: >> We've known about this for, um, decades: btree_gist's support for >> inet/cidr is fundamentally broken [1][2]. It's still there >> only because nobody's been able to think of a way of removing it >> without causing pain for anyone who has indexes like that. >> But maybe we should just accept that it's going to cause pain >> and remove it. > I think correctness should take priority over avoiding pain. Yeah. I spent a little time investigating this today, and hope to have a patch to propose tomorrow. regards, tom lane