On 2019/01/29 11:46 AM, Silvio wrote:
Additionally, I did the same test on the successfully converted database (an MVStore one, that is). Same results: OOM when trying this in read-only mode and successful without that option.
The "read-only" mode of H2 is I'm afraid not very well tested, and tends to go against the grain of most of the code, so it often results in surprising things.
For example, in read-only mode we don't currently create temporary files for large result sets, instead we buffer everything in memory.
That is hold-over from when we created temp files next to the database file, since we now use the OS' temp-filesystem, we should probably be using temp files again there.
You might want to try the LAZY_QUERY_EXECUTION=1 stuff, which acts a bit like a server-side cursor, and also prevents (some) temporary result set creation.
-- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
