---
title: "Comment by David Kurtz on \"Query Rewrite - My Story of a Performance Nightmare\" | Hashnode"
description: "I would expect a complete refresh to invalidate cursors on those materialized views. I have successfully used fast refreshed materialized views in a high-parse"
url: "https://hashnode.com/posts/query-rewrite-my-story-of-a-performance-nightmare/662e404658beadbf834b8a13/comment/662f7c30421c789ec3521ec2"
---

[Discussion](https://hashnode.com/posts/query-rewrite-my-story-of-a-performance-nightmare/662e404658beadbf834b8a13)

Comment [Query Rewrite - My Story of a Performance Nightmare](https://hashnode.com/posts/query-rewrite-my-story-of-a-performance-nightmare/662e404658beadbf834b8a13)

[David Kurtz](https://hashnode.com/@DavidKurtz)

[Apr 29, 2024](https://hashnode.com/posts/query-rewrite-my-story-of-a-performance-nightmare/662e404658beadbf834b8a13/comment/662f7c30421c789ec3521ec2)

I would expect a complete refresh to invalidate cursors on those materialized views.  
I have successfully used fast refreshed materialized views in a high-parse environment (to introduce HCC on Exadata in PeopleSoft Financials). The parse is a symptom. The question is what is the cause of so much parse, and why is it such a problem for you?

[Caro Krützmann](https://hashnode.com/@caroKruetzi)

[Apr 29, 2024](https://hashnode.com/posts/query-rewrite-my-story-of-a-performance-nightmare/662e404658beadbf834b8a13/comment/662f7c30421c789ec3521ec2#reply-662fec8c0f24760be6bd4c17)

Hi David, I think the real problem was a series of bad decisions :D I also think that Query Rewrite is not bad at all. The behavior was unexpected and should be checked before implementing MViews with such an option. But I think this is applies for any technical solution.
