Anything and everything you do in a program takes time -- the question is if/when/where it takes too much time. Executing a DB query does not necessarily take too much time. Once you have your DB connection established, doing 3 queries instead of 2, for example, does not necessarily mean you're adding a bunch of processing time. If, in order to avoid that 3rd query, you instead have to read a config file with the association of values to texts and then process it to find the desired text, you may well take more time than just doing the query in the first place.
We have a web service at work that gets hammered during peak hours (hundreds of requests per minute) that on average probably does a about 2 dozen queries per call, and typical end-to-end processing is maybe half a second per web service request (2 web servers, just 1 DB server shared by them). So really I would not lose sleep over one more simple select query. 🙂 Now, that's not to say you can't consider other alternatives, but make sure that you're sure those other alternatives are, in fact, measurably and noticeably faster, or you may be wasting time and creating needless complexity for a false sense of optimization.