| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | exclusion(at)gmail(dot)com |
| Subject: | BUG #19000: gist index returns inconsistent result with gist_inet_ops |
| Date: | 2025-07-27 05:00:02 |
| Message-ID: | 19000-2525470d200672ab@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 19000
Logged by: Alexander Lakhin
Email address: exclusion(at)gmail(dot)com
PostgreSQL version: 18beta2
Operating system: Ubuntu 24.04
Description:
The following script:
CREATE EXTENSION btree_gist;
CREATE TABLE t AS SELECT '192.168.1.0/25'::inet AS i;
SELECT * FROM t WHERE i << '192.168.1.0/24'::cidr;
i
----------------
192.168.1.0/25
CREATE INDEX ON t USING gist(i);
SELECT * FROM t WHERE i << '192.168.1.0/24'::cidr;
i
---
(0 rows)
shows an inconsistency when using the "<<" operator with a gist index.
Reproduced starting from be1cc9aaf.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-07-27 22:29:58 | Re: Lower priority of the configure option --with-libraries causes wrong lib resolution |
| Previous Message | David G. Johnston | 2025-07-25 16:22:12 | Re: BUG #18999: Equivalent queries processing WHERE IS NULL & WHERE IS NOT NULL produce mutually exclusive results |