Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
Date: 2025-08-01 02:38:31
Message-ID: CAMbWs48sCRUbz0CmkPSFEH8G1b9y-erq6rqYpA0sPhb_ZmwOpQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Aug 1, 2025 at 3:17 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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.

Thanks
Richard

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-08-01 03:33:28 Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
Previous Message Peter Geoghegan 2025-07-31 22:12:32 Re: Postgres: Queries are too slow after upgrading to PG17 from PG15