Hmmm, I think what is happening here is that when in MVCC mode with
transaction isolation level TRANSACTION_READ_COMMITTED, the session is
somehow seeing LOB entries that have already been deleted.
Thomas, does that ring any bells?
I've been through the code paths that end up in LobStorage, but I can't
see any obvious problems.
On 2012-12-03 09:58, Noel Grandin wrote:
Nice work on creating the test case!
Interesting, this is a genuine bug somewhere in the LOB code, and it
manifests even with MVCC=false.
The only short-term fix I can see is to set your transaction isolation
to TRANSACTION_REPEATABLE_READ.
Thomas, I further reduced the test-case, and I'm including it here.
Note that (for me) it did not fail every single time. I normally let
it run for about 15 seconds, and then terminate and try again.
I get a failure rate of about 50%.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
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.
