On Sunday, 6 January 2019 23:15:55 UTC+8, Diego Rivera wrote: > > Evgenij, can you elaborate on what "issues" arose with "specific use > cases" with regards to MULTI_THREADED? > For example, SELECT may skip rows that are concurrently updated in another thread and transaction. 1.4.197 and older versions are affected. With current sources such failures are not reproducible.
> but that the issues remain with PageStore - is this what you meant by > "specific use cases"? > I meant some issues in 1.4.197 with MVStore + MULTI_THREADED=TRUE. Combination of PageStore with multi-threaded kernel is not tested on regular basis, there are some known failures, but AFAIK nobody works on them, PageStore is an old fallback backend. Also it is not always suitable for multi-threaded access due to table-level locks. If you use PageStore with MULTI_THREADED=TRUE, you're on your own, be careful and perform some tests with your statements on heavy load. I can only say that multi-threaded PageStore definitely has problems with LOBs, so if you have BLOB or CLOB columns you should not use this combination of settings. LOCK_MODE=0 also cannot be set with multi-threaded PageStore, but there is no good reason for doing it anyway. -- 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.
