Hey team, quick question. I have a table which is ...
# general
l
Hey team, quick question. I have a table which is roughly 60 GB in size. It contains fields which I commonly have to join on, and I am currently using Trino to accomplish this. I have been considering if it makes sense to make this a dimension table. I know there are size constraints, but I could easily store it on disk. My worry though is that I've seen a comment mentioning the entire table may be stored on the heap. Is that the case, or can I get away with a 60GB dimension table?
Anyone able to help answer this?
m
Yes, the current impl is heap based.
l
Thank you @Mayank