From customer:

We've been having some problems with the performance when introducing the daily worklog. At this moment we have almost 1.000.000 records in the worklog table, and we notice that each time tempo accessed the table, all records were read and it spend almost three seconds. The query was something like this:
SELECT ID, issueid, AUTHOR, grouplevel, rolelevel, worklogbody, CREATED, UPDATEAUTHOR, UPDATED, STARTDATE, timeworked FROM worklog WHERE (STARTDATE >= '2013-07-15 00:00:00.0' ) AND (STARTDATE < '2013-07-16 00:00:00.0' ) AND (AUTHOR = 'elspina' );
We created a index with this syntax and the time went down to less than one second. We also noticed that only the records from the user were read, as intended.
CREATE INDEX worklog_author ON worklog (AUTHOR);
It would be great if you include this index in future releases.