I am working with a database on Amazon RDS and have a specific query which joins about 6 tables on keys. Creating the materialised view with data takes about 3 minutes and behaves as expected with minimal database load, but attempting to refresh the materialized view brings the database down by exhausting the 32GB memory available to the instance in under 5 minutes.

Is there any explanation for this inconsistent behaviour or way to anticipate it to avoid bringing down the database instance?

  • 1
    Are you using refresh ... concurrently? Nov 22 at 11:31
  • No - and the matview has no indexes at all.
    – Cong Chen
    Nov 22 at 12:59
  • Apologies - I use refresh materialized view with no concurrently.
    – Cong Chen
    Nov 22 at 13:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.