| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
| 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 03:33:28 |
| Message-ID: | 2189027.1754019208@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Richard Guo <guofenglinux(at)gmail(dot)com> writes:
> 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.
Yeah. I spent a little time investigating this today, and hope
to have a patch to propose tomorrow.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexandra Wang | 2025-08-01 03:41:17 | Re: BUG #16961: Could not access status of transaction |
| Previous Message | Richard Guo | 2025-08-01 02:38:31 | Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops |