Re: [h2] MVStore -- can I ignore it?

MV_STORE is a completely separate storage engine from the old PageStore. The old PageStore engine generates files with a .h2.db extension, the new MV_STORE engine generates files with a .mv.db extension. So it's not possible to mix and match opening the same files with the different engines. I

Re: [h2] Re: The last stable release Version 1.3.176 was published at 2014-04-05, when will 1.4.x stable version release?

We already require java7 for current 1.4​ -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send

[h2] MVStore -- can I ignore it?

So after managing to resolve my slow console launch problem , I'm back to actually working with h2. First question: what version to use? I was on 1.3.167 but would like to use something more up to date. 1.3.176 still gives me

[h2] Re: Please help, h2 console in El Capitan very very slow!!!

Update: with the help of someone over at stackexchange I managed to get rid of "Santa's MacBook Pro", and inetTester now resolves in 77ms. The key thing was setting

[h2] Re: The last stable release Version 1.3.176 was published at 2014-04-05, when will 1.4.x stable version release?

I have this same question. Is H2 still a product you can base any level of 'production' on, considering no stable release for years and still have to build with now completely obsolete java 1.6 (I removed some lines from the pom and was able to build with java7 but don't want to use such build

Re: [h2] Concurrency at org.h2.store.fs.FileBase.read()

Not without changing the structure considerably - FileBase inherits from java.nio.channels.FileChannel, which has a position field, and multiple things changing that at the same time would cause problems. We'd probably need to switch to using Java's asynchronous IO API to avoid that, which is

[h2] Concurrency at org.h2.store.fs.FileBase.read()

Hi I see a lot of thread blocked at java.lang.Thread.State: BLOCKED (on object monitor) at org.h2.store.fs.FileBase.read(FileBase.java:39) - waiting to lock <0x0006f1dfcdd0> (a org.h2.store.fs.FileSplit) at org.h2.mvstore.DataUtils.readFully(DataUtils.java:421) at

Re: [h2] SELECT FOR UPDATE does not work with MERGE

we don't currently have an answer for that, other than "be careful what order you do your MERGE statements in" because MERGE will take a full-table lock even in MVCC mode, and, as you found out, if you do MERGE statements in different orders in different transactions, you will get a timeout.

Re: [h2] SELECT FOR UPDATE does not work with MERGE

Really? It seems to work with UPDATE. I tested it with H2 console and using attached test with UPDATE instead of MERGE If SELECT FOR UPDATE doesn't work what On Tuesday, December 20, 2016 at 2:30:45 PM UTC+5, Noel Grandin wrote: > > SELECT FOR UPDATE doesn't actually do anything useful in

Re: [h2] SELECT FOR UPDATE does not work with MERGE

SELECT FOR UPDATE doesn't actually do anything useful in MVCC mode, I'm afraid. -- 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

[h2] SELECT FOR UPDATE does not work with MERGE

Hi Please see attached file: I added method testConcurrentMergeDeadlock() to existing test. This test failed with error ... Caused by: java.lang.IllegalStateException: Entry is locked [1.4.193/101] at org.h2.mvstore.DataUtils.newIllegalStateException(DataUtils.java:766) The same test with