Timeline for PostgreSQL Operator Class for index support of custom operator
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 25, 2021 at 14:38 | comment | added | Erwin Brandstetter | This is remarkable, but also misleading. The btree index is used because it's smaller than the table, so the index-only scan is faster than a sequential scan on the table. The performance gain is limited, though, and diminished if index-only scans are not possible. And the index is not used in its capacity as index. A non-selective condition like WHERE domains IS NOT NULL will be faster (still "using" the index) than a very selective condition like WHERE 'www.foo12345%' <~~ ANY(domains)! IOW, the index is barely supporting your custom operator as requested. | |
| Sep 9, 2019 at 17:40 | vote | accept | maxTrialfire | ||
| Sep 9, 2019 at 17:40 | history | answered | maxTrialfire | CC BY-SA 4.0 |