Activity log for bug #119780

Date Who What changed Old value New value Message
2007-06-11 04:42:26 Stuart Bishop bug added bug
2007-06-11 04:46:58 Stuart Bishop launchpad: status Unconfirmed Confirmed
2007-06-11 04:46:58 Stuart Bishop launchpad: importance Undecided High
2007-06-11 04:46:58 Stuart Bishop launchpad: statusexplanation
2007-06-11 04:46:58 Stuart Bishop launchpad: assignee stub
2007-06-14 14:19:14 Diogo Matsubara launchpad: importance High Medium
2007-06-14 14:19:14 Diogo Matsubara launchpad: statusexplanation <kiko> Is there a workaround for this issue? <stub> No. We need to revert the indexes or put up with it until it is fixed upstream. Lowering importance since it happens only using specific search terms as seen by OOPS-523A69 and OOPS-524C471. Meanwhile stub will poke psgsql developer regarding the GIN limitations.
2007-07-24 12:15:28 Stuart Bishop launchpad: status Confirmed In Progress
2007-07-24 12:15:28 Stuart Bishop launchpad: statusexplanation Stuart, do you plan to revert in the next rollout?
2007-08-05 09:48:39 Stuart Bishop launchpad: status In Progress Fix Released
2007-08-31 07:11:00 Stuart Bishop launchpad: status Fix Released Confirmed
2007-09-11 17:58:25 Christian Reis launchpad: assignee stub bjornt
2007-11-08 16:47:29 Joey Stanford launchpad: milestone 1.1.10 1.1.11
2007-11-29 06:19:22 Björn Tillenius launchpad: milestone 1.1.11 1.1.12
2008-01-23 19:16:51 Björn Tillenius description On production: 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 We need to try reporting this upstream, because if the index is dropped, the query works - addition of an index should not block queries from working, as the index should not be involved at all if full table scan is needed. 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.
2008-01-23 19:16:51 Björn Tillenius title GIN indexes cause some slow queries to fail entirely GIN indexes cause some searches of bug comments to fail
2008-01-23 19:17:16 Björn Tillenius launchpad: milestone 1.1.12
2009-09-08 06:58:20 Björn Tillenius malone: assignee Björn Tillenius (bjornt)
2011-09-20 19:51:02 Robert Collins 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
2011-09-21 08:05:45 Stuart Bishop launchpad: status Triaged Fix Released
2011-09-21 08:05:51 Stuart Bishop launchpad: assignee Stuart Bishop (stub)