Logged In: YES 
user_id=244310

Sorry for bothering you again, but I can reproduce the
problem on a different machine, even in a new installed
tracker, too.

My postgresql and roundup:
ii  postgresql     7.4.3-1 
ii  roundup        0.7.5-1 

How to reproduce:
* install & initialize new tracker
* start the web-frontend
* create a issue, set admin and anonymous on the nosy list
* go to the search page, create a search which will match
   the issue you have created in the previous step
* add a nosy=1 condition to search URI

You'll run into trouble as you tell postgresql you want to
have a join of issue_nosy with priority, although you are
accessing _issue's columns in the join. That's why the order
is important.

Perhaps, I should have added this comment when I created
this issue, sorry.