3 ms·
Thanks for the interesting link on IVM - I hadn’t heard about that work. Crikey, it’s a humbling one to solve generally reading through that page. I have a cas
by aidos 7y ago
Thanks for the interesting link on IVM - I hadn’t heard about that work. Crikey, it’s a humbling one to solve generally reading through that page.
I have a case of this where I do the incremental updates myself. In my case, figuring out which rows have changed isn’t that tough, I’ve got time stamps to lean on that simplify the process. More complex is that even plucking the data for a single row is slow if you’re not careful. I have a number of large subqueries that Postgres doesn’t optimise well if I just restrict the rows once in the outer query. Instead I need to be very specific with my restrictions in a number of duplicated locations throughout the query to get fast incremental updates. It works well now it’s up and running but it’s a little clumsy to set up.
- paulddraper 7y agoIt gets much easier if you are willing to perform "extra" query work to update the view. IVM is taking a sophisticated approach that results in a minimum of required work, even in cases of (some) aggregations.