Hi,
Thank you for your feedback. We are looking a little bit more into your memory issues. Now as Lukas said - there can be couple of things that are kept in your memory and are preventing another result set to get fetched.
About your questions:
- There are no special memory requirements for running the query. So memory issues with result sets should mean no obstacles to run another query, however to display the query result - that's a whole other story.
- Whenever you run query and keep the editor opened, everything from the result set you have fetched stays in memory until you close the editor or run another query in that editor. Our threshold is set to keep 30% of usable memory free so the system and our application stays viable. After that we consider the memory full and prevent the editors to fetch more rows from the result sets.
- Another thing is when you export the result set into CSV or Excel file, we keep in memory as many rows as we can during the process until the memory is "full". After that the rest of the exported rows are being streamed directly into csv/excel and not being kept in memory anymore. Therefore it's usualy a good idea to close the query editor after exporting a large result set thus freeing the memory.
Another memory greedy feature is the Statements since the whole query history with saved results is also kept in the memory. As Lukas wrote - the size of the history can be adjusted.
Thanks to you we have found out there has been some kind of memory leak in the query editors so closing the editor didn't necessarily have to free the memory used by its result set. Hopefuly this could solve your issue in the next release.
Please keep us posted if any of your issues remains in the next releases.
Regards,
Vladimír