If I am reading the translation of your post correctly, you have identified a memory-leak that occurs while using MVCC on an in-memory database, and you are look for a work-around.
Perhaps one of the least elegant solutions may be to make the database cached (or "on disk") and located in a temporary folder/directory. That said, Thomas M. should look at it, because it sounds like a bug. On Tuesday, November 20, 2012 9:18:29 PM UTC+13, sug wrote: > > Now, H2DataBase version 1.3.168 is used. > Although MVCC is used in in memory mode, the phenomenon in which the size > of a memory continues becoming large has occurred. > > When not using MVCC in in-memory mode, the same phenomenon does not occur. > > Can't MVCC be used when using in memory mode? > If there is an evasion measure, may I teach and have? > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/S59OuF-kR9IJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
