Query timeouts with PG result in traceback

[anonymous]

In trac.adiumx.com search select :tickets, wikis, and changesets; search for "tor" (without the quotes).
This is the effect:

If you think this really should work and you can reproduce it, you should consider reporting this problem to the Trac team.

Go to http://trac.edgewall.org/ and create a new ticket where you describe the problem, how to reproduce it. Don't forget to include the Python traceback found below.

TracGuide — The Trac User and Administration Guide
Python Traceback

Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 406, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 237, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/lib/python2.4/site-packages/trac/Search.py", line 181, in process_request
    results += list(source.get_search_results(req, terms, filters))
  File "/usr/lib/python2.4/site-packages/trac/ticket/api.py", line 269, in get_search_results
    args + args2)
  File "/usr/lib/python2.4/site-packages/trac/db/util.py", line 50, in execute
    return self.cursor.execute(sql_escape_percent(sql), args)
  File "/usr/lib/python2.4/site-packages/trac/db/util.py", line 50, in execute
    return self.cursor.execute(sql_escape_percent(sql), args)
ProgrammingError: canceling statement due to statement timeout

[anonymous]

This only seems to happen when searching for tor.

[thatch]

This is a db timeout, caused (my guess) by too many results. Adium's Trac is using postgres with a query timeout, and the timeout is doing its job...

Searching for other short sequences which appear often in larger words ("are", for example) results in the same error. Should we handle this and give a prettier error?

[cboos]

Maybe yes, depends on #6348 then.