Huge load on database if a trigger expression contains a user macro

When history syncer tries to evaluate a trigger expression it makes a SQL query to database which selects all unique hostid related to the trigger.
The query is performed for each trigger having a user macro.

We should use cache instead of SQL queries in this case.