Scheduled daily reports consistently return a out of out of memory error

Re-running the report works but the scheduled run consistently breaks. Does anybody else have experience with this?

2replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Hi Kevin Li !

    Thanks for reaching out and sorry for the delayed response! This is an error thrown from your Postgresql database. It's possible that the memory you currently have in your database to execute your queries does not meet what is required to run them. It's possible that when you ran the report, all of your queries were hitting your database at the same time and this can cause an overload on the database side. Could you chat with your database admin and see if you can increase the memory? Here are a couple Postgresql forums that might be somewhat of a help to you:

    https://dba.stackexchange.com/questions/64570/postgresql-error-out-of-memory

    https://www.postgresql.org/message-id/4057e37d0fad0814281017dc6c211c00.squirrel@sq.gransy.com

    Like
  • A memory error means that your program has ran out of memory. If you get an unexpected MemoryError and you think you should have plenty of RAM available, it might be because you are using a 32-bit python installation. This could be caused by either the 2GB per program limit imposed by Windows (32bit programs), or lack of available RAM on your computer. The easy solution, if you have a 64-bit operating system, is to switch to a 64-bit installation of python. The issue is that 32-bit python only has access to ~4GB of RAM. This can shrink even further if your operating system is 32-bit, because of the operating system overhead.

    Like
Like Follow
  • 1 mth agoLast active
  • 2Replies
  • 49Views
  • 3 Following