bug comment full text search is disabled - GIN indices in pg 8.2 do not support table scans
Bug #119780 reported by
Stuart Bishop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Stuart Bishop |
Bug Description
Currently searching in bug comments is disabled, since it needs use to use a GIN index (for performance). When using a GIN index, searches that are too general fail, similar to this:
launchpad_prod=# select person.id from person where person.fti @@ ftq('-lt');
ERROR: Query requires full scan, GIN doesn't support it
Seen in OOPS-524C471
To workaround this we need to look at the querytree() described in Stuart's comment below, and only do the actual search if we know that we will get back a result. After we've done this, we should search in bug comments again.
Changed in launchpad: | |
status: | In Progress → Fix Released |
Changed in launchpad: | |
milestone: | 1.1.10 → 1.1.11 |
Changed in launchpad: | |
milestone: | 1.1.11 → 1.1.12 |
description: | updated |
Changed in launchpad: | |
milestone: | 1.1.12 → none |
Changed in malone: | |
assignee: | Björn Tillenius (bjornt) → nobody |
summary: |
- GIN indexes cause some searches of bug comments to fail + bug comment full text search is disabled - GIN indices in pg 8.2 do not + support table scans |
To post a comment you must log in.
Known about:
http:// archives. postgresql. org/pgsql- hackers/ 2007-01/ msg01581. php