Comment 7 for bug 866100

Sorting by something on bugtask (e.g. importance our default) might improve things too.

The index_scan_backwards was the primary cause of slowness : postgresql will sometimes stubbornly use a matching sort index when one exists even though the data being shown may not be current on that index (which leads to loads of misses).