MAX_MEMORY_ROWS is the one you want On Wed, 13 Apr 2022 at 16:12, Ron Exxon <[email protected]> wrote:
> I have a query that returns a very large result set, which gets overflowed > to disk in a size that is too large. The environment has ample memory to > handle this result set, however I haven't been able to find which > configuration parameter controls the maximum in-memory size for a result > set. > I have tried CACHE_SIZE and MAX_MEMORY_ROWS and neither seemed to have an > impact on the overflow. > Can anybody point me to what I'm missing? Any help is greatly appreciated > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/h2-database/c29b4f34-20af-44ba-9610-37e870624e9dn%40googlegroups.com > <https://groups.google.com/d/msgid/h2-database/c29b4f34-20af-44ba-9610-37e870624e9dn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/CAFYHVnWCpUsOFJ9AHLOspSeCMyM6eU%2Bn3ewNNdc-XJjgV%2BT_sA%40mail.gmail.com.
