Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
| От | Tom Lane |
|---|---|
| Тема | Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops |
| Дата | |
| Msg-id | 2197759.1754024003@sss.pgh.pa.us обсуждение |
| Ответ на | Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops (Tender Wang <tndrwang@gmail.com>) |
| Список | pgsql-bugs |
Tender Wang <tndrwang@gmail.com> writes:
> Tom Lane <tgl@sss.pgh.pa.us> 于2025年8月1日周五 11:33写道:
>> Richard Guo <guofenglinux@gmail.com> writes:
>>> On Fri, Aug 1, 2025 at 3:17 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>>> We've known about this for, um, decades: btree_gist's support for
>>>> inet/cidr is fundamentally broken [1][2].
> What I debugged yesterday was, in gbt_inet_consistent(),
> query = convert_network_to_scalar(dquery, INETOID, &failure);
Right --- as I mentioned in one of the linked threads, the thing that
is fundamentally wrong here is relying on convert_network_to_scalar
in the first place. That has no charter to deliver exact results,
and it doesn't. In the present example I think the issue is that
it doesn't consider the netmask at all; but there are many other
cases where it's not an exact representation of inet's sort order.
That's not a big problem for its intended purpose for statistical
estimates, but it's completely fatal for index infrastructure.
regards, tom lane
В списке pgsql-bugs по дате отправления: