Design patterns to avoiding breaking the SRP while performing heavy data logging

Question

A class that performs both computations and data logging* seems to have at least two responsibilities. Given a system for which the specifications require heavy data logging, what kind of design patterns or architectural patterns can be used to avoid bloating all the classes with logging calls every time they compute something?

The decorator pattern be used (e.g. Interpolator decorated to LoggingInterpolator), but it seems that would result in a situation hardly more desirable in which almost every major class would need to be decorated with logging.

*Note: When I wrote this, I was working in a context in which it was called logging, but it was actually writing to a database. I'm not particularly referring issuing debug or error messages in a log4net log or the like.