How does Timescale handle lookup tables?

That is, "I have this seldomly-updated list of ~10000 things, and I'm going to need to join it against my time-series data."

With other time-series databases I've dealt with, it's an afterthought at best and the answer is typically "Enrich the data via flink/benthos/etc. on import and avoid using any kind of join."

Does Timescale's use of PostgreSQL circumvent this issue, both in terms of storage of lookup tables, and performance on join?