3 ms·
This is much clearer thank you. From your initial example, I thought you were suggesting to just load 2 large tables into memory at once and iterate through the
by torme 16y ago
This is much clearer thank you. From your initial example, I thought you were suggesting to just load 2 large tables into memory at once and iterate through them to find matches.
Also, at the surface, this seems like it would be a good application for using materialized views. I obviously don't know the ins and outs of what the usage here was, but this seems like a case where slowing down the insert would be a good speed sacrifice for retrieval.
I'm not going to even feign being an expert at database optimization, but that seems like it might be a more efficient way to approach it.
- iaskwhy 16y agoI actually didn't know about materialized views but from what I've read it seems like this wouldn't be a good place to put it to work just because the conditions on the calendar where changed pretty frequently (most of them weren't, like I said on my previous post, but some were and from that I read that could be a problem since the view needed to be updated frequently). It feels really good to learn something new, I'm thinking of some scenarios which might improve with this type of views, thanks!