3 ms·
Wow, this is amazing. Just the other day I was staring at a query with multiple CTEs that took 20+ seconds to run. Ended up adding an additional WHERE clause on
by Zanfa 4y ago
Wow, this is amazing. Just the other day I was staring at a query with multiple CTEs that took 20+ seconds to run. Ended up adding an additional WHERE clause on an indexed column to the slowest CTE, which took the execution time down to 100s of ms.
Just tried the original query, but with explicitly not materialized CTEs and the runtime was basically as fast as the manually pre-filtered solution.
- srcreigh 4y agoNot materializing lets Postgres push extra where clauses and join conditions into the CTE so this makes sense! Now you know why I spam all the “CTEs are amazing” threads about materialization (there have been 5 or so in the last few months)